| 2.1 |
Approval of the agenda |
|
| R2-2500001 |
Agenda for RAN2#129 |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2500002 |
RAN2#128 Meeting Report |
MCC |
| 2.5 |
Others |
|
| R2-2500003 |
RAN2 Handbook |
MCC |
| R2-2501458 |
Guidelines on writing a CR |
MCC |
| R2-2501587 |
Clarification of the chapter title to match the description of the UE History Information |
R3 (Nokia, ZTE, CMCC) |
| R2-2501588 |
Stage 2 correction for network slice support during XN handover |
R3 (Ericsson, JIO Platforms (JPL), AT&T, Rakuten, FiberCop, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia, Huawei, Samsung, ZTE, CMCC) |
| R2-2501589 |
Stage 2 correction on DL LBT failure information |
R3 (Ericsson, Nokia) |
| R2-2501590 |
Correction on handover failure due to unavailable candidate relay UE |
R3 (Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Huawei) |
| R2-2501603 |
Stage 2 correction for network slice support during XN handover |
R3 (Ericsson, JIO Platforms (JPL), AT&T, Rakuten, FiberCop, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia, Huawei, Samsung, ZTE, CMCC) |
| R2-2501604 |
Stage 2 correction on DL LBT failure information |
R3 (Ericsson, Nokia) |
| 3 |
Incoming liaisons |
|
| R2-2500005 |
LS on draft-ietf-raw-technologies, "Reliable and Available Wireless Technologies" (contact: Huawei) |
IETF DetNet |
| 4.1 |
EUTRA corrections Rel-17 and earlier |
|
| R2-2500369 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| R2-2500371 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| R2-2500372 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| R2-2500462 |
Detection of consecutive HARQ feedback failures in NB-IoT NTN |
Google |
| R2-2500938 |
Clarification on Inclination value description |
THALES |
| R2-2500939 |
Clarification on Inclination value description |
THALES |
| R2-2500956 |
First reconfiguration after reestablishment with SN-terminated bearers |
Huawei, HiSilicon |
| R2-2500957 |
First reconfiguration after reestablishment with SN-terminated bearers |
Huawei, HiSilicon |
| R2-2500958 |
First reconfiguration after reestablishment with SN-terminated bearers |
Huawei, HiSilicon |
| R2-2500959 |
First reconfiguration after reestablishment with SN-terminated bearers |
Huawei, HiSilicon |
| R2-2501114 |
Correction on the UE behaviours upon setting CEF report |
Huawei, HiSilicon |
| R2-2501115 |
Correction on the UE behaviours upon setting CEF report |
Huawei, HiSilicon |
| R2-2501146 |
Clarification on the mapping of RSRP thresholds to CE levels |
MediaTek Inc. |
| R2-2501356 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| R2-2501357 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| R2-2501358 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| R2-2501402 |
Clarification on Inclination value description |
THALES |
| R2-2501407 |
Clarification on Inclination value description |
THALES |
| R2-2501541 |
Clarification on Inclination value description |
THALES |
| R2-2501542 |
Clarification on Inclination value description |
THALES |
| R2-2501562 |
Clarification on Inclination value description |
Thales |
| R2-2501563 |
Clarification on Inclination value description |
Thales |
| R2-2501594 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| R2-2501595 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| R2-2501596 |
Correction on MPDCCH parameter in PUR-Config |
ZTE Corporation, Sanechips, Ericsson, Huawei, HiSilicon |
| 5.1.1 |
Stage 2 and Organisational |
|
| R2-2500116 |
Correction on L3 beam filtering |
OPPO, Apple, Nokia (Rapporteur) |
| R2-2500117 |
Correction on L3 beam filtering |
OPPO, Apple, Nokia (Rapporteur) |
| R2-2500118 |
Correction on L3 beam filtering |
OPPO, Apple, Nokia (Rapporteur) |
| R2-2500119 |
Correction on L3 beam filtering |
OPPO, Apple, Nokia (Rapporteur) |
| R2-2500984 |
Clarification on support of BFD-BFR on PSCell |
Ericsson, ZTE Corporation |
| R2-2500985 |
Clarification on support of BFD-BFR on PSCell |
Ericsson, ZTE Corporation |
| R2-2500986 |
Clarification on support of BFD-BFR on PSCell |
Ericsson, ZTE Corporation |
| R2-2500987 |
Clarification on support of BFD-BFR on PSCell |
Ericsson, ZTE Corporation |
| R2-2501359 |
Clarification on support of BFD-BFR on PSCell |
Ericsson, ZTE Corporation |
| R2-2501360 |
Clarification on support of BFD-BFR on PSCell |
Ericsson, ZTE Corporation |
| R2-2501361 |
Clarification on support of BFD-BFR on PSCell |
Ericsson, ZTE Corporation |
| R2-2501362 |
Clarification on support of BFD-BFR on PSCell |
Ericsson, ZTE Corporation |
| R2-2501379 |
Clarification on supported features on the PSCell |
Ericsson |
| R2-2501380 |
Clarification on supported features on the PSCell |
Ericsson |
| R2-2501381 |
Clarification on supported features on the PSCell |
Ericsson |
| R2-2501382 |
Clarification on supported features on the PSCell |
Ericsson |
| 5.1.2.1 |
MAC |
|
| R2-2500515 |
Corrections on PDCCH monitoring |
Samsung (Rapporteur), Huawei, HiSilicon, Ericsson |
| R2-2500516 |
Corrections on PDCCH monitoring |
Samsung (Rapporteur), Ericsson |
| R2-2500517 |
Corrections on PDCCH monitoring |
Samsung (Rapporteur), Huawei, HiSilicon, Ericsson |
| R2-2501171 |
Corrections on PDCCH monitoring |
Samsung (Rapporteur), Huawei, HiSilicon, Ericsson, Sharp |
| R2-2501172 |
Corrections on PDCCH monitoring |
Samsung (Rapporteur), Huawei, HiSilicon, Ericsson, Sharp |
| R2-2501173 |
Corrections on PDCCH monitoring |
Samsung (Rapporteur), Huawei, HiSilicon, Ericsson, Sharp |
| R2-2501493 |
Corrections on PDCCH monitoring |
Samsung (Rapporteur), Huawei, HiSilicon, Ericsson, Sharp |
| R2-2501494 |
Corrections on PDCCH monitoring |
Samsung (Rapporteur), Huawei, HiSilicon, Ericsson, Sharp |
| 5.1.3.1 |
NR RRC |
|
| R2-2500032 |
LS on AdditionalSpectrumEmission in NR SL Pre-configuration (R4-2418075; contact: LGE) |
RAN4 |
| R2-2500713 |
Clarification on RRC procedure delay for BWP switching |
Samsung |
| R2-2500786 |
Clarification on RRC procedure delay for BWP switching |
Samsung |
| R2-2500787 |
Clarification on RRC procedure delay for BWP switching |
Samsung |
| R2-2500788 |
Clarification on RRC procedure delay for BWP switching |
Samsung |
| R2-2500901 |
Correction on sidelink RRC specification |
ZTE Corporation, Sanechips |
| R2-2500902 |
Correction on sidelink RRC specification |
ZTE Corporation, Sanechips |
| R2-2500903 |
Correction on sidelink RRC specification |
ZTE Corporation, Sanechips |
| R2-2501098 |
Discussion on change of si-SchedulingInfo for SIB6, SIB7 and SIB8 |
vivo |
| R2-2501099 |
Clarification on change of si-SchedulingInfo for SIB6, SIB7 and SIB8 (R15) |
vivo |
| R2-2501100 |
Clarification on change of si-SchedulingInfo for SIB6, SIB7 and SIB8 (R16) |
vivo |
| R2-2501101 |
Clarification on change of si-SchedulingInfo for SIB6, SIB7 and SIB8 (R17) |
vivo |
| R2-2501102 |
Clarification on change of si-SchedulingInfo for SIB6, SIB7 and SIB8 (R18) |
vivo |
| R2-2501351 |
Correction on sidelink RRC specification |
ZTE Corporation, Sanechips |
| R2-2501352 |
Correction on sidelink RRC specification |
ZTE Corporation, Sanechips |
| R2-2501353 |
Correction on sidelink RRC specification |
ZTE Corporation, Sanechips |
| R2-2501383 |
Reply LS on AdditionalSpectrumEmission |
RAN2 |
| 5.1.3.2 |
UE capabilities |
|
| R2-2500445 |
Correction on the mandatory features for IAB-MT |
ZTE Corporation, Sanechips, Qualcomm, Ericsson, Xiaomi, Samsung |
| R2-2500446 |
Correction on the mandatory features for IAB-MT |
ZTE Corporation, Sanechips, Qualcomm, Ericsson, Xiaomi, Samsung |
| R2-2500447 |
Correction on the mandatory features for IAB-MT and NCR-MT |
ZTE Corporation, Sanechips, Qualcomm, Ericsson, Xiaomi, Samsung |
| R2-2500594 |
Correction to simultaneous BWP switch across CCs |
Apple |
| R2-2500595 |
Correction to simultaneous BWP switch across CCs |
Apple |
| R2-2500596 |
Correction to simultaneous BWP switch across CCs |
Apple |
| R2-2500841 |
Correction on the IAB-MT capability |
Huawei, HiSilicon, Samsung, Qualcomm Incorporated, Nokia, NEC, Fujitsu |
| R2-2500842 |
Correction on the IAB-MT capability |
Huawei, HiSilicon, Samsung, Qualcomm Incorporated, Nokia, NEC, Fujitsu |
| R2-2500843 |
Correction on the IAB-MT capability |
Huawei, HiSilicon, Samsung, Qualcomm Incorporated, Nokia, NEC, Fujitsu |
| R2-2500931 |
Further aspects to consider for UE capability segmentation in LTE |
Ericsson |
| R2-2501116 |
Discussion on SRS capability reporting for SRS only cell |
Huawei, HiSilicon |
| R2-2501363 |
LS on segmented UE capabilities |
RAN2 |
| R2-2501592 |
Correction on the mandatory features for IAB-MT |
ZTE Corporation, Sanechips, Qualcomm, Ericsson, Xiaomi, Samsung |
| 5.3 |
NR Positioning Support |
|
| R2-2500817 |
Correction on SP positioning SRS (de-)activation MAC CE |
Huawei, HiSilicon |
| R2-2500818 |
Correction on SP positioning SRS (de-)activation MAC CE |
Huawei, HiSilicon |
| R2-2500819 |
Correction on SP positioning SRS (de-)activation MAC CE |
Huawei, HiSilicon |
| 6.1.1 |
Stage 2 and Organisational |
|
| R2-2500017 |
Reply LS on UL RRC message segmentation for UECapabilityInformation (R3-247769; contact: Qualcomm) |
RAN3 |
| R2-2500382 |
Minor correction in the description of RAN Visible QoE Measurements |
Lenovo |
| R2-2500383 |
Minor correction in the description of RAN Visible QoE Measurements |
Lenovo |
| R2-2500597 |
Definition of NTN Cell |
Apple |
| R2-2500598 |
Definition of NTN Cell |
Apple |
| 6.1.2 |
User Plane corrections |
|
| R2-2500940 |
Clarification on Inclination value description |
THALES |
| R2-2501175 |
On association between RLC entities and PDCP entity |
Huawei, HiSilicon |
| R2-2501239 |
Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE |
R2 |
| R2-2501240 |
Correction on Spatial Relation Activation/Deactivation For PUCCH Repetition |
ZTE Corporation |
| R2-2501298 |
Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE |
R2 |
| R2-2501299 |
Correction on Spatial Relation Activation/Deactivation For PUCCH Repetition |
ZTE Corporation |
| R2-2501302 |
Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE |
R2 |
| R2-2501303 |
Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE |
R2 |
| R2-2501314 |
Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE |
ZTE Corporation |
| R2-2501315 |
Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE |
ZTE Corporation |
| 6.1.3 |
Control Plane corrections |
|
| R2-2500882 |
Corrections to ntn-PolarizationUL |
Ericsson |
| R2-2500883 |
Corrections to ntn-PolarizationUL |
Ericsson |
| R2-2500941 |
Clarification on Inclination value description |
THALES |
| R2-2501403 |
Clarification on Inclination value description |
THALES |
| R2-2501408 |
Clarification on Inclination value description |
THALES |
| R2-2501409 |
Corrections to ntn-PolarizationUL |
Ericsson |
| R2-2501410 |
Corrections to ntn-PolarizationUL |
Ericsson |
| R2-2501543 |
Clarification on Inclination value description |
THALES |
| R2-2501544 |
Clarification on Inclination value description |
THALES |
| R2-2501545 |
Corrections to ntn-PolarizationUL |
Ericsson |
| R2-2501546 |
Corrections to ntn-PolarizationUL |
Ericsson |
| R2-2501564 |
Clarification on Inclination value description |
Thales |
| R2-2501565 |
Clarification on Inclination value description |
Thales |
| R2-2501584 |
Corrections to ntn-PolarizationUL |
Ericsson |
| R2-2501585 |
Corrections to ntn-PolarizationUL |
Ericsson |
| 6.1.3.1 |
NR RRC |
|
| R2-2500439 |
Correction on SCS and CP configuration in RedCap-specific initial BWP |
ZTE Corporation, Sanechips |
| R2-2500440 |
Correction on SCS and CP configuration in RedCap-specific initial BWP |
ZTE Corporation, Sanechips |
| R2-2500677 |
Correction on implicit RLM for mTRP operation |
Ericsson |
| R2-2500683 |
Correction on implicit RLM for mTRP operation |
Ericsson |
| R2-2500696 |
Correction to smtc2 |
Huawei, HiSilicon |
| R2-2500697 |
Correction to smtc2 |
Huawei, HiSilicon |
| R2-2500767 |
Corrections to NTN SMTC configuration |
ZTE Corporation, Ericsson, Sanechips |
| R2-2500768 |
Corrections to NTN SMTC configuration |
ZTE Corporation, Ericsson, Sanechips |
| R2-2500822 |
Corrections on SRB4 |
Samsung, Ericsson |
| R2-2500880 |
Miscellaneous non-controversial corrections Set XXIV |
Ericsson |
| R2-2500914 |
Correction on UE capability check when logging last HO type |
Ericsson |
| R2-2500915 |
Correction on UE capability check when logging last HO type |
Ericsson |
| R2-2500960 |
Configuration of UL power control in unified TCI framework |
Huawei, HiSilicon |
| R2-2500961 |
Configuration of UL power control in unified TCI framework |
Huawei, HiSilicon |
| R2-2501112 |
Discussion on logging suspension due to IDC |
Huawei, HiSilicon |
| R2-2501206 |
Correction on the CSI-AperiodicTriggerStateList for aperiodic enhanced group-based beam reporting in R17 |
vivo |
| R2-2501207 |
Correction on the CSI-AperiodicTriggerStateList for aperiodic enhanced group-based beam reporting in R18 |
vivo |
| R2-2501323 |
Clarification for IDC solutions of logged MDT (Rel-17) |
OPPO, CMCC |
| R2-2501324 |
Clarification for IDC solutions of logged MDT (Rel-18) |
OPPO, CMCC |
| R2-2501337 |
Discussion on logging suspension due to IDC |
Huawei, HiSilicon, CMCC, OPPO |
| R2-2501364 |
Corrections on SRB4 |
Samsung, Ericsson |
| R2-2501365 |
Miscellaneous non-controversial corrections Set XXIV |
Ericsson |
| R2-2501411 |
Correction to smtc2 |
Huawei, HiSilicon |
| R2-2501413 |
Corrections to NTN SMTC configuration |
ZTE Corporation, Ericsson, Sanechips |
| R2-2501414 |
Corrections to NTN SMTC configuration |
ZTE Corporation, Ericsson, Sanechips |
| R2-2501533 |
Configuration of UL power control in unified TCI framework |
Huawei, HiSilicon |
| R2-2501561 |
Correction to smtc2 |
Huawei, HiSilicon |
| R2-2501566 |
Corrections to NTN SMTC configuration |
ZTE Corporation, Ericsson, Sanechips |
| R2-2501567 |
Corrections to NTN SMTC configuration |
ZTE Corporation, Ericsson, Sanechips |
| 6.1.3.2 |
UE capabilities |
|
| R2-2500120 |
Left Issue on Maximum Number of UL Segments |
OPPO |
| R2-2500384 |
Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] |
Lenovo |
| R2-2500385 |
Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] |
Lenovo |
| R2-2500711 |
Clarification on FRx_xDD Differentiation in per UE Capability for NTN bands |
vivo, Xiaomi |
| R2-2500712 |
Clarification on FRx_xDD Differentiation in per UE Capability for NTN bands |
vivo, Xiaomi |
| R2-2501148 |
UE Capability for SCell activation with TCI activation configuration |
MediaTek Inc. |
| R2-2501149 |
UE Capability for SCell activation with TCI activation configuration |
MediaTek Inc. |
| R2-2501150 |
UE Capability for SCell activation with TCI activation configuration |
MediaTek Inc. |
| R2-2501151 |
UE Capability for SCell activation with TCI activation configuration |
MediaTek Inc. |
| R2-2501187 |
Discussion on inconsistent reporting of NR SA capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2501188 |
Clarification to UL RRC segmentation |
Nokia, Nokia Shanghai Bell |
| R2-2501189 |
Clarification to UL RRC segmentation |
Nokia, Nokia Shanghai Bell |
| R2-2501327 |
Left Issue on Maximum Number of UL Segments |
OPPO |
| R2-2501366 |
Clarification on rrc-MaxCapaSegAllowed[ Max-RRC-SegUL] |
OPPO |
| R2-2501367 |
Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] |
Lenovo |
| R2-2501368 |
Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] |
Lenovo |
| R2-2501369 |
Clarification to UL RRC segmentation |
Nokia, Nokia Shanghai Bell |
| R2-2501370 |
Clarification to UL RRC segmentation |
Nokia, Nokia Shanghai Bell |
| R2-2501371 |
UE Capability for SCell activation with TCI activation configuration |
MediaTek Inc. |
| R2-2501372 |
UE Capability for SCell activation with TCI activation configuration |
MediaTek Inc. |
| R2-2501373 |
UE Capability for SCell activation with TCI activation configuration |
MediaTek Inc. |
| R2-2501374 |
UE Capability for SCell activation with TCI activation configuration |
MediaTek Inc. |
| R2-2501375 |
Summary of [AT129][608][Maint] |
Nokia (Rapporteur) |
| R2-2501386 |
Clarification on rrc-MaxCapaSegAllowed [Max-RRC-SegUL] |
OPPO |
| R2-2501398 |
Clarification on rrc-MaxCapaSegAllowed [Max-RRC-SegUL] |
OPPO |
| R2-2501399 |
Clarification on rrc-MaxCapaSegAllowed [Max-RRC-SegUL] |
OPPO |
| R2-2501400 |
Clarificatiion on rrc-MaxCapaSegAllowed |
OPPO |
| R2-2501404 |
Clarification on FRx_xDD Differentiation in per UE Capability for NTN bands |
vivo, Xiaomi |
| R2-2501405 |
Clarification on FRx_xDD Differentiation in per UE Capability for NTN bands |
vivo, Xiaomi |
| R2-2501406 |
Clarification on FRx_xDD Differentiation in per UE Capability for NTN bands |
vivo, Xiaomi |
| R2-2501437 |
Clarification on rrc-MaxCapaSegAllowed [Max-RRC-SegUL] |
OPPO |
| R2-2501550 |
Clarification on FRx Differentiation in per UE Capability for NTN bands |
vivo, Xiaomi |
| R2-2501597 |
Clarification to UL RRC segmentation |
Nokia, Nokia Shanghai Bell |
| R2-2501599 |
Clarification on FRx_xDD Differentiation in per UE Capability for NTN bands |
vivo, Xiaomi |
| 6.1.3.3 |
Other |
|
| R2-2500357 |
Correction on the pre-condition of UE applying CN controlled subgroup ID for PEI in R17 |
vivo |
| R2-2500358 |
Correction on the pre-condition of UE applying CN controlled subgroup ID for PEI in R18 |
vivo |
| R2-2500359 |
Correction on the pre-condition of UE applying CN controlled subgroup ID for PEI in R17 |
vivo |
| R2-2500360 |
Correction on the pre-condition of UE applying CN controlled subgroup ID for PEI in R18 |
vivo |
| R2-2500599 |
Definition of NTN Cell |
Apple |
| R2-2500600 |
Definition of NTN Cell |
Apple |
| 6.2 |
NR Sidelink relay |
|
| R2-2500316 |
RRC Connection Establishment for Multihop-Parallel Relay |
IIT, Kharagpur |
| R2-2500325 |
Data distribution and HARQ management for multihop-parallel relay topology in 5G NR |
IIT, Kharagpur |
| R2-2500908 |
Miscellaneous corrections for Rel-17 SL relay |
ZTE Corporation, Sanechips |
| R2-2500909 |
Miscellaneous corrections for Rel-17 SL relay |
ZTE Corporation, Sanechips |
| 6.3 |
NR positioning enhancements |
|
| R2-2500602 |
Correction on spatial relation info in SP SRS activation deactivation MAC CE (R17) |
ZTE Corporation, Ericsson, Qualcomm, CATT, Samsung, vivo, Nokia, Xiaomi |
| R2-2500603 |
Correction on spatial relation info in SP SRS activation deactivation MAC CE (R18) |
ZTE Corporation, Ericsson, Qualcomm, CATT, Samsung, vivo, Nokia, Xiaomi |
| R2-2500813 |
Correction to BDS issue of data indication |
Huawei, HiSilicon |
| R2-2500814 |
Correction to BDS issue of data indication |
Huawei, HiSilicon |
| R2-2500815 |
Correction to PRS priority subset for DL-AoD |
Huawei, HiSilicon, Ericsson, VIVO, Samsung |
| R2-2500816 |
Correction to PRS priority subset for DL-AoD |
Huawei, HiSilicon, Ericsson, VIVO, Samsung |
| R2-2501422 |
Correction to PRS priority subset for DL-AoD |
Huawei, HiSilicon, Ericsson, VIVO, Samsung |
| R2-2501423 |
Correction to PRS priority subset for DL-AoD |
Huawei, HiSilicon, Ericsson, VIVO, Samsung |
| R2-2501600 |
Correction to PRS priority subset for DL-AoD |
Huawei, HiSilicon, Ericsson, VIVO, Samsung |
| 6.6 |
NR Sidelink enhancements |
|
| R2-2500427 |
Discussion on procedure descriptions of SL-DRX |
Apple, Ericsson, Qualcomm |
| R2-2500428 |
Correction on SL DRX procedure |
Apple, Ericsson |
| R2-2500429 |
Correction on SL DRX procedure |
Apple, Ericsson |
| R2-2500430 |
Correction on SL DRX configurations for GC/BC |
Apple, Ericsson |
| R2-2500431 |
Correction on SL DRX configurations for GC/BC |
Apple, Ericsson |
| R2-2500872 |
Correction to MAC on IUC |
Ericsson |
| R2-2500873 |
Correction to MAC on IUC |
Ericsson |
| R2-2501474 |
Correction on SL DRX procedure |
Apple, Ericsson |
| R2-2501475 |
Correction on SL DRX procedure |
Apple, Ericsson |
| R2-2501476 |
Correction to MAC on IUC |
Ericsson |
| R2-2501477 |
Correction to MAC on IUC |
Ericsson |
| R2-2501601 |
Correction on SL DRX procedure |
Apple, Ericsson |
| 7.0.1 |
UE Capabilities |
|
| R2-2500006 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#119 (R1-2410665; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2500266 |
Introduction of Rel-18 UE feature list |
Xiaomi |
| R2-2500267 |
Miscellaneous updates for SL relay and MC capabilities |
Xiaomi |
| R2-2501226 |
Consideration on the STx2P UE Feature (40-6-3a-1/40-6-3b-2) |
ZTE Corporation |
| R2-2501227 |
[Draft] LS on the STx2P UE Feature |
ZTE Corporation |
| R2-2501237 |
Introduction of Rel-18 UE feature list |
Xiaomi |
| R2-2501457 |
Introduction of Rel-18 UE feature list |
Xiaomi |
| R2-2501512 |
[Draft] Reply LS on the STx2P UE Features |
ZTE |
| R2-2501516 |
Reply LS on the STx2P UE Features |
RAN2 |
| R2-2501573 |
Introduction of Rel-18 UE feature list |
Xiaomi |
| R2-2501574 |
Capability updates for RAN1 feature list |
Xiaomi |
| R2-2501575 |
Capability updates for MC and RAN1 feature list |
Xiaomi |
| 7.0.2.1 |
RACH-less HO |
|
| R2-2500409 |
Correction on SR-triggered RACH regarding RACH-less HO |
ASUSTeK |
| R2-2500809 |
Rapporteur CR for RACH-less LTM and HO [RACH-lessHO] |
Huawei, HiSilicon, CATT, Samsung, Qualcomm |
| R2-2501247 |
Rapporteur CR for RACH-less HO and LTM [RACH-lessHO] |
Huawei, HiSilicon, CATT, Qualcomm, Samsung |
| R2-2501535 |
Rapporteur CR for RACH-less HO and LTM [RACH-lessHO] |
Huawei, HiSilicon, CATT, Qualcomm, Samsung |
| 7.0.2.2 |
NR network-controlled repeaters |
|
| R2-2500202 |
Correction on the NCR-MT capability |
Huawei, HiSilicon, Samsung, Qualcomm Incorporated, Nokia, NEC, Fujitsu |
| R2-2500441 |
Views on SRB2 capability for NCR-MT and IAB-MT |
ZTE Corporation, Sanechips, Ericsson, Xiaomi, China Telecom |
| R2-2501390 |
Dummy the capability bit nonDRB-NCR-r18 |
ZTE Corporation, Ericsson, Samsung, Qualcomm, Nokia, China Telecom, Fujitsu, NEC |
| R2-2501391 |
Dummy the capability bit nonDRB-NCR-r18 |
ZTE Corporation, Ericsson, Samsung, Qualcomm, Nokia, China Telecom, Fujitsu, NEC |
| R2-2501552 |
Report of [AT129][009][NCR] UE capability |
ZTE |
| R2-2501559 |
Correction on the NCR-MT capability |
Huawei |
| R2-2501560 |
Correction on the NCR-MT capability |
Huawei |
| 7.0.2.3 |
NR support for UAV |
|
| R2-2500231 |
Clarification on the content of event Hy measurement report |
CATT, Qualcomm Inc., CMCC |
| R2-2500232 |
Correction on the content of event Hy measurement report |
CATT, Qualcomm Inc., CMCC |
| R2-2500317 |
Integration of Lifi Features in UAS for IoT Application |
IIT, Kharagpur |
| 7.0.2.8 |
Enhanced support of reduced capability NR devices |
|
| R2-2501279 |
Correction on eDRX for UE in RRC_INACTIVE |
ZTE Corporation, Sanechips |
| 7.0.2.10 |
Network energy savings for NR |
|
| R2-2500395 |
Measurements on the carrier of SSB-less SCell |
NEC |
| R2-2500555 |
SSBLess handling |
Nokia |
| R2-2500693 |
Discussion on servingCellMO for SSB-less Scell |
Huawei, HiSilicon, Apple, Qualcomm Incorporated |
| R2-2501313 |
Clarification On SP CSI Reporting Activation/Deactivation For 8Tx |
ZTE Corporation |
| R2-2501571 |
Correction On SP CSI Reporting Activation/Deactivation MAC CE |
ZTE Corporation |
| 7.0.2.11 |
Further enhancement of data collection for SON MDT in NR and EN-DC |
|
| R2-2500233 |
Corrections on SPR determination |
CATT |
| R2-2500849 |
Miscellaneous corrections for SON/MDT |
Samsung, Ericsson |
| R2-2501376 |
Corrections on SPR determination |
CATT |
| R2-2501377 |
Miscellaneous corrections for SON/MDT |
Samsung, Ericsson |
| R2-2501598 |
Miscellaneous corrections for SON/MDT |
Samsung, Ericsson |
| 7.0.2.12 |
Dual Transmission/Reception (Tx/Rx) Multi-SIM for NR |
|
| R2-2501224 |
Correction to the MUSIM Timer Processing for the Reconfiguration with Sync Case |
ZTE Corporation |
| R2-2501268 |
Corrections on MUSIM gap |
Samsung |
| R2-2501511 |
Corrections on MUSIM gap |
Samsung |
| 7.0.2.13 |
NR MIMO evolution |
|
| R2-2500009 |
LS on Precoder Indication for 8-Port CG-PUSCH (R1-2410836; contact: Google) |
RAN1 |
| R2-2500013 |
LS on condition of applying both indicated TCI states for PDCCH reception (R1-2410916; contact: Samsung) |
RAN1 |
| R2-2500107 |
Introduction of RRC parameters for 8-port CG-PUSCH |
Google |
| R2-2500157 |
Correction to applied TCI state for mTRP PDCCH reception |
Samsung |
| R2-2500410 |
Correction on supporting 8Tx in MAC specification - method 2 |
ASUSTeK |
| R2-2500709 |
Remaining details on TDD UL/DL Configuration for Two TA |
Ericsson |
| R2-2500710 |
Correction on TDD UL/DL Configuration for Two TA |
Ericsson |
| R2-2500726 |
Correction on Precoder Indication for 8-Port CG-PUSCH |
Ericsson |
| R2-2501117 |
Correction on pusch-DMRS8Tx-r18 |
Huawei, HiSilicon |
| R2-2501238 |
Clarification On SP CSI Reporting Activation/Deactivation For 8Tx |
R2 |
| R2-2501297 |
Clarification On SP CSI Reporting Activation/Deactivation For 8Tx |
R2 |
| R2-2501301 |
Clarification On SP CSI Reporting Activation/Deactivation For 8Tx |
R2 |
| R2-2501441 |
Introduction of RRC parameters for 8-port CG-PUSCH |
Google, Ericsson |
| R2-2501442 |
Correction on TDD UL/DL Configuration for Two TA |
Ericsson |
| R2-2501447 |
Correction to applied TCI state for mTRP PDCCH reception |
Samsung |
| R2-2501448 |
Correction on TDD UL/DL Configuration for Two TA |
Ericsson |
| 7.0.2.14 |
Enhancements of NR Multicast and Broadcast Services |
|
| R2-2500024 |
LS on Update of Broadcast MCCH Information (R3-247892; contact: Nokia) |
RAN3 |
| R2-2500139 |
Reply LS on Update of Broadcast MCCH Information |
Nokia Corporation |
| R2-2500205 |
Clarification on the terminology of new cell |
Huawei, HiSilicon, Ericsson, Sharp, Samsung, Nokia, CATT, ZTE |
| R2-2500699 |
On multicast MCCH information acquisition |
Samsung |
| R2-2500829 |
Clarification on determining the cell in which Multicast was configured in RRC_CONNECTED |
ZTE Corporation, Ericsson, Nokia, Samsung |
| R2-2500830 |
Discussion on the LS of Broadcast MCCH update |
ZTE Corporation, Sanechips |
| R2-2501341 |
Reply LS on Update of Broadcast MCCH Information |
RAN2 |
| R2-2501342 |
Clarification on the terminology of new cell |
Huawei, HiSilicon, Ericsson, Sharp, Samsung, Nokia, CATT, ZTE |
| R2-2501343 |
Clarification on determining the cell in which Multicast was configured in RRC_CONNECTED |
ZTE Corporation, Ericsson, Nokia, Samsung |
| R2-2501593 |
Clarification on determining the cell in which Multicast was configured in RRC_CONNECTED |
ZTE Corporation, Ericsson, Nokia, Samsung |
| 7.0.2.15 |
Enhancement on NR QoE management and optimizations for diverse services |
|
| R2-2500022 |
LS on QMC Coordination for RRC Segmentation in NR-DC (R3-247888; contact: ZTE) |
RAN3 |
| R2-2500054 |
LS Reply on MBS Communication Service Type (S4-242151; contact: Huawei) |
SA4 |
| R2-2500386 |
Clean-up corrections on stage 2 description of QMC |
Lenovo |
| R2-2500546 |
Discussion on RRC segmentation coordination for QoE reporting in NR-DC |
Nokia, Nokia Shanghai Bell |
| R2-2500774 |
Miscellaneous corrections for QoE report |
ZTE Corporation, Sanechips |
| R2-2500775 |
Reply LS on QMC Coordination for RRC Segmentation in NR-DC |
ZTE Corporation, Sanechips |
| R2-2500828 |
Corrections on SRB(s) for QoE measurements |
Samsung, Ericsson |
| R2-2500850 |
Discussion on RRC issues for QoE |
Ericsson |
| R2-2501344 |
Report of [AT129][502][QoE] SRB4/SRB5 segmentation configuration (Ericsson) |
Ericsson |
| R2-2501345 |
Clean-up corrections on stage 2 description of QMC |
Lenovo |
| R2-2501346 |
Corrections on QoE |
Samsung, Ericsson |
| R2-2501396 |
Reply LS on QMC Coordination for RRC Segmentation in NR-DC |
RAN2 |
| R2-2501397 |
Miscellaneous corrections for QoE report |
ZTE Corporation, Sanechips |
| 7.0.2.16 |
XR Enhancements for NR |
|
| R2-2500023 |
LS on PDCP SN gap report handling during UE mobility (R3-247891; contact: Huawei) |
RAN3 |
| R2-2500089 |
Discussion on PDCP SN gaps during mobility |
Qualcomm Incorporated |
| R2-2500181 |
Further Discussion on the SN Gap Report |
CATT |
| R2-2500491 |
Discussion of RAN3 LS on PDCP SN Gap report handling |
Nokia, Nokia Shanghai Bell |
| R2-2500492 |
Analysis of current text on transmission of PDCP SN Gap report |
Nokia, Nokia Shanghai Bell |
| R2-2500688 |
Correction on RA Stopping for XR |
Samsung |
| R2-2500722 |
Stage 2 correction on delay status reporting |
Lenovo, Nokia (rapporteur) |
| R2-2500894 |
Discussion on DSR cancellation in DC |
Huawei, HiSilicon |
| R2-2500895 |
Discussion on PDCP SN gap report handling during UE mobility |
Huawei, HiSilicon |
| R2-2500896 |
Correction on UE assistance information for XR |
Huawei, HiSilicon |
| R2-2500928 |
Correction on PDCP SN Gap Report – Triggering Condition and Reporting |
Ericsson |
| R2-2501011 |
PDCP SN Gap report Corrections |
Nokia, Nokia Shanghai Bell |
| R2-2501125 |
Correction to PDCP SN gap report |
Huawei, HiSilicon |
| R2-2501349 |
Reply on PDCP SN gap report handling during UE mobility |
RAN2 |
| R2-2501492 |
Correction on RA Stopping for XR |
Samsung |
| R2-2501496 |
Offline #013 on PDCP SN Gap Reporting |
Nokia (Rapporteur) |
| R2-2501506 |
PDCP SN Gap report Corrections |
Nokia, Ericsson, Nokia Shanghai Bell |
| 7.0.2.17 |
TEI18 |
|
| R2-2500388 |
RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) |
Peraton Labs |
| R2-2500389 |
RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) |
Peraton Labs |
| R2-2501339 |
RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) |
Peraton Labs, AT&T, Verizon |
| R2-2501340 |
RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) |
Peraton Labs, AT&T, Verizon |
| R2-2501536 |
RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) [MPS_RNAU_ResumeCause] |
Peraton Labs, CISA ECD, FirstNet, AT&T, Verizon, Samsung, Qualcomm |
| R2-2501537 |
RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) [MPS_RNAU_ResumeCause] |
Peraton Labs, CISA ECD, FirstNet, AT&T, Verizon, Samsung, Qualcomm |
| R2-2501538 |
RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) [MPS_RNAU_ResumeCause] |
Peraton Labs, CISA ECD, FirstNet, AT&T, Verizon, Samsung, Qualcomm |
| R2-2501539 |
RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) [MPS_RNAU_ResumeCause] |
Peraton Labs, CISA ECD, FirstNet, AT&T, Verizon, Samsung, Qualcomm |
| 7.0.2.18 |
Others |
|
| R2-2500881 |
Miscellaneous non-controversial corrections Set XXIV |
Ericsson |
| R2-2501300 |
Correction on number of Rx branches supported by a UE |
Nokia |
| R2-2501591 |
Miscellaneous non-controversial corrections Set XXIV |
Ericsson |
| 7.1.1 |
Organizational |
|
| R2-2500007 |
Reply LS on CBR range (R1-2410708; contact: CATT) |
RAN1 |
| R2-2500276 |
Corrections of SL CBR Range and level related parameters |
CATT, Ericsson |
| 7.1.3 |
SLPP corrections |
|
| R2-2500845 |
Missing additional measurements for SL-TDOA and SL-TOA |
Qualcomm Incorporated |
| R2-2501424 |
Missing additional measurements for SL-TDOA and SL-TOA |
Qualcomm Incorporated |
| 7.1.5 |
RRC corrections |
|
| R2-2500166 |
RRC Sidelink Positioning Correction |
Fraunhofer IIS, Fraunhofer HHI, Ericsson |
| R2-2500277 |
Corrections on activation of non-preconfigured SRS with the type of semi-persistent |
CATT, Ericsson, Qualcomm Incorporated, ZTE Corporation, Samsung |
| R2-2500812 |
Correction to sidelinkUEInformation for SL-PRS shared resource pool |
Huawei, HiSilicon, Vivo |
| R2-2500971 |
Low Power High Accuracy Positioning Correction |
Ericsson |
| R2-2501425 |
RRC Sidelink Positioning Correction |
Fraunhofer IIS, Fraunhofer HHI, Ericsson |
| R2-2501426 |
Corrections on activation of non-preconfigured SRS with the type of semi-persistent |
CATT, Ericsson, Qualcomm Incorporated, ZTE Corporation, Samsung |
| R2-2501432 |
Correction to sidelinkUEInformation for SL-PRS shared resource pool |
Huawei, HiSilicon, Vivo |
| R2-2501436 |
Corrections on activation of non-preconfigured SRS with the type of semi-persistent |
CATT, Ericsson, Qualcomm Incorporated, ZTE Corporation, Samsung, Huawei, Xiaomi |
| 7.1.6 |
MAC corrections |
|
| R2-2500513 |
Miscellaneous corrections on SL-PRS |
ASUSTeK |
| R2-2500545 |
Correction on parameters for SL-PRS for configured grant Type 1 |
Sharp |
| R2-2500604 |
Correction on SRS hopping in positioning |
ZTE Corporation |
| R2-2501427 |
Miscellaneous corrections on SL-PRS |
ASUSTeK, ZTE, Huawei, HiSilicon |
| R2-2501428 |
Correction on SRS hopping in positioning |
ZTE Corporation |
| R2-2501434 |
Correction to UTW for positioning SRS frequency hopping |
Huawei, HiSilicon |
| R2-2501515 |
Report of [406] MAC impact on UTW |
ZTE Corporation |
| 7.2 |
Further NR mobility enhancements |
|
| R2-2500035 |
LS on UE capability for fast RRC processing for LTM (R4-2420125; contact: MediaTek) |
RAN4 |
| R2-2500038 |
Reply LS on the fast RRC processing for LTM (R4-2420218; contact: Ericsson) |
RAN4 |
| R2-2500151 |
Rel-18 LTM issues |
MediaTek Inc. |
| R2-2500173 |
Corrections related to random access for LTM |
Samsung |
| R2-2500228 |
Correction on UE-based TA measurement |
CATT |
| R2-2500333 |
On the Remaining Rel-18 LTM Aspects and Corrections |
Nokia |
| R2-2500356 |
Remaining issues on LTM and conditional reconfiguration |
vivo |
| R2-2500374 |
reverting variable for LTM |
Ofinno, LLC |
| R2-2500540 |
Removal of prerequisite of ltm-FastProcessingConfig-r18 |
MediaTek Inc. |
| R2-2500728 |
Discussion on LTM cell switch with CFRA |
Google Korea LLC |
| R2-2500962 |
Corrections to TS 38.300 and 38.331 for LTM |
Huawei, HiSilicon |
| R2-2500963 |
MAC CR rapporteur summary |
Huawei, HiSilicon |
| R2-2500988 |
Remaining issues on LTM |
Ericsson, MediaTek Inc. |
| R2-2500989 |
Discussion on the fast RRC processing for LTM |
Ericsson, MediaTek Inc. |
| R2-2500990 |
Summary of RRC proposals for feMob |
Ericsson |
| R2-2501196 |
Correction on LTM cell switch execution procedure |
Sharp |
| R2-2501294 |
Corrections for mobility enhancements in stage-2 |
ZTE Corporation, Ericsson |
| R2-2501295 |
Corrections on the field descriptions of selectedCondRRCReconfig and reportSlotConfig-r18 |
ZTE Corporation |
| R2-2501325 |
Corrections for mobility enhancements in stage-2 |
ZTE Corporation, Ericsson |
| R2-2501467 |
Removal of the prerequisite for ltm-FastProcessingConfig-r18 |
MediaTek Inc. |
| R2-2501468 |
Correction to LTM cell switch with CFRA |
Google |
| R2-2501469 |
Addition of missing need code in NZP-CSI-RS-Resource |
MediaTek Inc. |
| R2-2501482 |
Offline #114 on R18 LTM stage 2 correction |
Huawei (Rapporteur) |
| R2-2501486 |
Miscellaneous RRC corrections for feMob |
Ericsson |
| R2-2501489 |
Addition of missing need code in NZP-CSI-RS-Resource |
MediaTek Inc. |
| R2-2501520 |
Correction of mobility latency for LTM |
Huawei, HiSilicon, Nokia |
| R2-2501554 |
Correction to LTM cell switch with CFRA |
Google, Samsung |
| R2-2501558 |
Clarification on UE reporting unsupported target band in pdcch-RACH-AffectedBandsList-r18 |
MediaTek |
| 7.3.1 |
Organizational |
|
| R2-2500048 |
Reply LS on UE Location Information for NB-IoT NTN (S2-2412665; contact Qualcomm) |
SA2 |
| R2-2500077 |
Discussion on SA2 LS on UE Location Information for NB-IoT NTN |
vivo |
| R2-2500547 |
On SA2 LS for coarse UE location reporting in NB-IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2501309 |
Location information reporting for NB-IoT |
Ericsson |
| 7.3.2 |
Corrections |
|
| R2-2500203 |
Correction on drx-inactivityTimer |
Huawei, HiSilicon |
| R2-2501217 |
Correction on HARQ process |
Samsung |
| R2-2501269 |
Correction on GNSS procedure |
ZTE Corporation, Sanechips |
| R2-2501526 |
Correction on GNSS procedure |
ZTE Corporation, Sanechips |
| R2-2501527 |
Correction on drx-inactivityTimer |
Huawei, HiSilicon |
| R2-2501582 |
Correction on drx-inactivityTimer |
Huawei, HiSilicon |
| 7.4.1 |
Organizational |
|
| R2-2500033 |
LS on simultaneous operation between GNSS and NR NTN (R4-2419898; contact: Huawei) |
RAN4 |
| R2-2500042 |
Reply LS to RAN1 and RAN2 on FR2-NTN inclusion to specifications (R4-2420476; contact: vivo) |
RAN4 |
| R2-2501310 |
Remaining open issues in NR NTN |
Ericsson |
| 7.4.2 |
Corrections |
|
| R2-2500078 |
Discussion on RAN4 LS on Simultaneous Operation between GNSS and NR NTN |
vivo |
| R2-2500329 |
On SSBs from Source and Target Satellite in Soft Switching with Resynchronization |
Nokia, Nokia Shanghai Bell |
| R2-2500537 |
Discussion on RAN4 LS on IDC issue in NTN |
Qualcomm Incorporated |
| R2-2500584 |
Discussion on simultaneous GNSS and NTN operations |
Apple |
| R2-2500695 |
Corrections to NTN mobility |
Huawei, HiSilicon |
| R2-2500703 |
Discussion on simultaneous operation between GNSS and NR NTN |
Huawei, HiSilicon, Turkcell |
| R2-2500769 |
Consideration on VSAT UE capability report |
ZTE Corporation, Vivo, Sanechips |
| R2-2500942 |
Clarification on Inclination value description |
THALES |
| R2-2501292 |
Remaining open issues of satellite switch with resync |
Sequans Communications |
| R2-2501401 |
Consideration on VSAT UE capability report |
ZTE Corporation, Vivo, Sanechips |
| R2-2501547 |
Draft reply LS simultaneous operation between GNSS and NR NTN |
Nokia |
| R2-2501548 |
Correction to VSAT capability report |
ZTE Corporation, vivo, Sanechips |
| R2-2501549 |
Corrections to NTN mobility |
Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips, vivo, CMCC, CATT, Nokia, Nokia Shanghai Bell, Apple, Samsung, MediaTek Inc., Xiaomi, Interdigital |
| R2-2501568 |
Response LS on simultaneous operation between GNSS and NR NTN |
RAN2 |
| R2-2501569 |
Correction to VSAT UE capability report |
ZTE Corporation, vivo, Sanechips |
| R2-2501602 |
Correction to VSAT UE capability report |
ZTE Corporation, vivo, Sanechips |
| 7.5.3 |
Control plane corrections (including UE capabilities) |
|
| R2-2500411 |
Corrections to SidelinkUEInformationNR setting and E2E SL DRB release |
ASUSTeK |
| R2-2500567 |
Correction on indirect path failure information |
China Telecom, Huawei, HiSilicon |
| R2-2500802 |
Correction on T400 configuration |
Xiaomi, Apple |
| R2-2500907 |
Corrections for Rel-18 SL relay |
ZTE Corporation, Sanechips |
| R2-2501236 |
Correction to UE information transfer on sidelink |
Huawei, HiSilicon |
| R2-2501429 |
Correction to PC5 RLC channel handling |
Huawei, HiSilicon |
| R2-2501430 |
Correction to SidelinkUEInformationNR setting |
ASUSTeK |
| R2-2501431 |
Corrections for Rel-18 SL relay |
ZTE Corporation, Sanechips, China Telecom, Huawei, HiSilicon |
| 7.6 |
NR Sidelink evolution |
|
| R2-2500097 |
Discussion on left issue of MCSt |
LG Electronics Inc. |
| R2-2500101 |
Discussion on MCSt on PSFCH resource pool |
ZTE Corporation, Sanechips, Ericsson, Qualcomm |
| R2-2500102 |
Discussion on MCSt and PQI-CAPC mapping |
ZTE Corporation, Sanechips, Ericsson |
| R2-2500114 |
Remaining issues for MCSt |
OPPO |
| R2-2500169 |
Discussion on MCSt for multi-TB with PSFCH configured |
Huawei, HiSilicon |
| R2-2500412 |
Miscellaneous MAC Corrections on Sidelink |
ASUSTeK |
| R2-2500730 |
SL-Carrierfailure indication correction |
Lenovo |
| R2-2500875 |
Discussion on resource re-selection from SL LBT Failure indication |
Ericsson |
| R2-2500996 |
SL-Carrierfailure indication correction |
Lenovo |
| R2-2501140 |
MAC correction on Release-18 Sidelink evolution |
LG Electronics Inc. |
| R2-2501393 |
Discussion on MCSt |
ZTE Corporation, Sanechips |
| R2-2501478 |
Correction on MAC for MCSt |
ZTE Corporation, Sanechips, Ericsson |
| R2-2501479 |
Correction on 38.300 for MCSt |
ZTE Corporation, Sanechips |
| R2-2501480 |
Correction on PQI-CAPC mapping table |
ZTE Corporation, Sanechips |
| R2-2501481 |
Miscellaneous MAC Corrections on Sidelink |
ASUSTeK |
| R2-2501487 |
Correction on MAC for MCSt |
ZTE Corporation, Sanechips, Ericsson |
| R2-2501488 |
Correction on 38.300 for MCSt |
ZTE Corporation, Sanechips, Ericsson |
| R2-2501503 |
SL Resource reselection in case of LBT failure |
Ericsson |
| R2-2501504 |
Correction to MAC on resource reselection due to LBT failure |
Ericsson, LG |
| R2-2501576 |
Correction on 38.300 for MCSt |
ZTE Corporation, Sanechips, Ericsson |
| 7.8.1 |
RAN4 led items |
|
| R2-2500039 |
Reply LS on carrierBandwidth configuration for less-than-5MHz carriers (R4-2420382; contact: ZTE) |
RAN4 |
| R2-2500556 |
Less than 5Mhz and carrier configuration |
Nokia |
| R2-2500976 |
Correction on SIB22 broadcasting status |
Samsung |
| R2-2501190 |
Clarification to lower MSD capability |
Nokia |
| R2-2501208 |
Summary of [POST128][023][NR Other] NR_BWP (vivo) |
vivo |
| R2-2501209 |
Correction on UE capability for BWP_Wor (option 1) |
vivo |
| R2-2501210 |
Correction on UE capability for BWP_Wor (option2-306CR) |
vivo |
| R2-2501211 |
Correction on BWP operation without restriction for DC case (Option 2-300CR) |
vivo |
| R2-2501220 |
Clarification on the less than 5M Configuration |
ZTE Corporation |
| R2-2501221 |
Correction on the Less than 5M Configuration |
ZTE Corporation |
| R2-2501495 |
Correction on SIB22 broadcasting status |
Samsung |
| R2-2501505 |
[DRAFT] Reply LS to SA2 |
vivo |
| R2-2501507 |
Reply LS to SA2 |
RAN2 |
| R2-2501513 |
Correction on the Less than 5M Configuration |
ZTE Corporation |
| R2-2501540 |
Correction on UE capability for BWP_Wor |
vivo, Qualcomm Incorporated, Ericsson |
| R2-2501551 |
Clarification to lower MSD capability |
Nokia |
| 8.0 |
General |
|
| R2-2500004 |
UE usage of the RAT restrictions (C1-247193; contact: Apple) |
CT1 |
| R2-2500051 |
LS on energy saving indication from CN to RAN (S2-2413034; contact: Ericsson) |
SA2 |
| R2-2500055 |
LS on Time Synchronization for MBS (S4-242169; contact: Qualcomm) |
SA4 |
| R2-2500066 |
Reply LS on Time Synchronization for MBS (S2-2501327; contact: Ericsson) |
SA2 |
| R2-2500112 |
Discussion on RAT Restriction (C1-247193) |
OPPO |
| R2-2500435 |
RAN2 impact of WID ECRATU |
Apple, Vodafone, InterDigital, Ericsson |
| R2-2500436 |
Restriction on RAT utilization |
Apple, Vodafone, InterDigital, Ericsson |
| R2-2500437 |
Restriction on RAT utilization |
Apple, Vodafone, InterDigital, Ericsson |
| R2-2500438 |
Restriction on RAT utilization |
Apple, Vodafone, InterDigital, Ericsson |
| R2-2500521 |
Discussion on CT1 LS in R2-2500004/C1-247193 |
CATT |
| R2-2500550 |
RAT restrictions for ECRAT |
Nokia |
| R2-2500967 |
Restriction on RAT utilization |
Apple, Vodafone, InterDigital, Ericsson |
| R2-2501096 |
Time Synchronization for MBS |
Ericsson |
| R2-2501248 |
Improvements to specification handling |
Ericsson |
| R2-2501456 |
Plan for offline trial of Git |
Ericsson |
| R2-2501460 |
Report of [POST127][004][ASN.1 Modernization] Requirements |
Nokia |
| R2-2501500 |
Reply LS on Time Synchronization for MBS |
Ericsson |
| R2-2501509 |
Reply LS on Time Synchronization for MBS |
RAN2 |
| R2-2501518 |
Report on [AT129][005][Modernization] ASN.1 Review Modernization |
Nokia |
| R2-2501519 |
Reply LS on UE usage of the RAT restrictions |
RAN2 |
| R2-2501531 |
Restriction on RAT utilization |
Apple, Vodafone, InterDigital, Ericsson, Nokia, OPPO |
| R2-2501532 |
Restriction on RAT utilization |
Apple, Vodafone, InterDigital, Ericsson, Nokia, OPPO |
| R2-2501556 |
Reply LS on UE usage of the RAT restrictions |
RAN2 |
| 8.1.1 |
Organizational |
|
| R2-2500011 |
Reply LS on applicable functionality reporting for beam management UE-sided model (R1-2410898; contact: Samsung) |
RAN1 |
| R2-2500015 |
LS on signalling feasibility of dataset and parameter sharing (R1-2410922; contact: Qualcomm) |
RAN1 |
| R2-2500018 |
LS on per-UE UE performance metrics (R3-247775; contact: Huawei) |
RAN3 |
| R2-2500019 |
Reply LS on AIML data collection (R3-247801; contact: ZTE) |
RAN3 |
| R2-2500043 |
LS on AI/ML UE sided data collection (RP-243316; contact: InterDigital) |
RAN |
| R2-2500049 |
Reply LS on AIML data collection (S2-2412726; contact: InterDigital) |
SA2 |
| R2-2500053 |
Reply LS on AIML data collection (S3-245138; contact: Samsung) |
SA3 |
| R2-2500058 |
Reply LS on AIML Data Collection (S5-247219; contact: Nokia) |
SA5 |
| R2-2500059 |
Reply LS on AIML Data Collection (S5-247336; contact: Samsung) |
SA5 |
| R2-2500062 |
LS on LMF-based AI/ML Positioning for Case 2b (S2-2501133; contact: vivo) |
SA2 |
| R2-2500070 |
LS on LMF-based AI/ML Positioning for case 3b (S2-2501341; contact: Ericsson) |
SA2 |
| R2-2500123 |
Introduction of AI for Air interface feature in 38300 |
vivo(Rapporteur) |
| R2-2501263 |
Draft running RRC CR for AIML PHY |
Ericsson |
| R2-2501338 |
On the Running Stage 3 (38.331) CR |
Nokia |
| 8.1.2.2 |
LCM for UE-sided model for Beam Management use case |
|
| R2-2500121 |
Discussion on LCM for UE sided model |
NEC |
| R2-2500124 |
Discussion on LCM for UE-sided model for Beam Management |
vivo |
| R2-2500140 |
LCM for UE-sided model for BM |
LG Electronics |
| R2-2500152 |
Open Issues for Applicable Functionality Reporting for BM |
OPPO |
| R2-2500153 |
Open Issues for UE Request Triggered Data Collection Procedure for BM |
OPPO |
| R2-2500159 |
Discussion on LCM for UE-sided model for Beam Management |
Spreadtrum, UNISOC |
| R2-2500238 |
Discussion on LCM for UE-sided model for BM use case |
CATT |
| R2-2500259 |
Remaining issues on LCM procedure of UE-sided model for AI/ML based beam management |
Apple |
| R2-2500264 |
Functionality Applicability Reporting and Management |
Xiaomi |
| R2-2500320 |
Further Discussion on LCM for UE-side Model for AI-BM |
MediaTek Inc. |
| R2-2500392 |
On LCM for UE-sided Models for Beam Management |
Qualcomm Incorporated |
| R2-2500413 |
Discussion on LCM for UE-sided models |
ASUSTeK |
| R2-2500468 |
Discussion on LCM for UE-sided Model for Beam Management Use Case |
Fujitsu |
| R2-2500507 |
Discussion on LCM for UE-sided model for beam management |
Samsung |
| R2-2500568 |
LCM for UE-sided model for BM use case |
China Telecom |
| R2-2500611 |
LCM for UE-sided model in beam management |
Lenovo |
| R2-2500737 |
Some aspects for model monitoring on UE side |
Sony |
| R2-2500755 |
On LCM for UE-sided Model for Beam Management Use Case |
SHARP |
| R2-2500756 |
Further discussion on LCM for UE-sided model for BM |
Transsion Holdings |
| R2-2500835 |
Continuous Discussion On LCM for UE-sided model |
ZTE Corporation |
| R2-2500858 |
Discussion on LCM for UE-sided model for Beam Management use case |
Huawei, HiSilicon |
| R2-2500997 |
LCM for UE-side Beam Management |
Nokia |
| R2-2501048 |
Discussion on LCM for UE-sided model for BM |
CMCC |
| R2-2501079 |
Considerations on LCM for UE-sided model in Beam Management use case |
Kyocera |
| R2-2501103 |
LCM for UE-sided model for BM |
Google |
| R2-2501122 |
LCM for UE-sided model for Beam Management use case |
InterDigital |
| R2-2501218 |
Discussion on LCM for UE-Side Model for Beam Management use case |
Futurewei Technologies |
| R2-2501230 |
Discussion on LCM for UE-sided model for BM use case |
TCL |
| R2-2501262 |
LCM for UE-side models for beam management |
Ericsson |
| R2-2501517 |
Summary of offline discussion [AT129][026][AI Phy] Signaling for BM |
Ericsson |
| 8.1.2.3 |
LCM for Positioning use case |
|
| R2-2500125 |
Discussion on left issues and Reply LS on AIML enhanced positioning |
vivo |
| R2-2500174 |
Association of measurements and ground truth labels for positioning use-cases |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2500239 |
Consideration on LCM for Positioning use case |
CATT |
| R2-2500260 |
Remaining issues on LCM procedure of AI/ML based positioning |
Apple |
| R2-2500294 |
LCM for Positioning use case |
NEC |
| R2-2500469 |
Discussion on LCM for Positioning Use Case |
Fujitsu |
| R2-2500501 |
Discussion on the LCM for AI positioning case 1 |
Xiaomi |
| R2-2500569 |
LCM for UE-sided model for positioning use case |
China Telecom |
| R2-2500605 |
Discussion on LCM for positioning use case |
ZTE Corporation |
| R2-2500612 |
LCM for AIML based positioning with UE-sided model |
Lenovo |
| R2-2500638 |
Discussion on LCM for POS use case |
Samsung |
| R2-2500847 |
LCM for positioning use case |
Qualcomm Incorporated |
| R2-2500968 |
Report of [POST128][026][AIML] LCM Procedure for Positioning Case1 (Ericsson) |
Ericsson |
| R2-2500969 |
LCM For Positioning |
Ericsson |
| R2-2500977 |
LMF control for UE reporting of changes in applicable functionalities |
Nokia |
| R2-2501031 |
Discussion on LCM for positioning |
CMCC |
| R2-2501109 |
Discussion on LCM for Positioning use case |
Huawei, HiSilicon |
| R2-2501123 |
LCM for Positioning use case |
InterDigital |
| R2-2501124 |
[DRAFT] Reply LS on LMF-based AIML Positioning for Case 2b |
InterDigital |
| R2-2501261 |
Discussion on Functionality-based LCM for Positioning Use Case |
CEWiT |
| 8.1.3 |
NW side data collection |
|
| R2-2500126 |
Discussion on NW side data collection |
vivo |
| R2-2500141 |
NW side data collection |
LG Electronics |
| R2-2500154 |
Data Collection for Network Side Model Training for BM |
OPPO |
| R2-2500160 |
Discussion on NW side data collection |
Spreadtrum, UNISOC |
| R2-2500240 |
Consideration on NW side data collection |
CATT |
| R2-2500261 |
Remaining issues on NW-sided data collection |
Apple |
| R2-2500285 |
Discussion on NW-side data collection |
NEC |
| R2-2500321 |
Further Discussion on NW-side Data Collection |
MediaTek Inc. |
| R2-2500391 |
On Network Side Data Collection |
Qualcomm Incorporated |
| R2-2500404 |
NW side data collection |
Interdigital Inc. |
| R2-2500470 |
Discussion on NW side Data Collection |
Fujitsu |
| R2-2500506 |
Disuccsion on NW side data collection |
Samsung |
| R2-2500574 |
Discussion on NW side data collection for AIML based beam management |
China Telecom |
| R2-2500613 |
Data collection for NW-sided model training |
Lenovo |
| R2-2500798 |
Discussion on NW side data collection |
Xiaomi |
| R2-2500838 |
Further Discussion on NW Side Data Collection |
ZTE Corporation |
| R2-2500888 |
Data Collection for Training of NW-side AI/ML Models |
Nokia |
| R2-2500893 |
Discussion on NW-sided data collection for training |
Huawei, HiSilicon |
| R2-2500999 |
Report on [POST128][019][AI PHY] NW side data collection (Nokia) |
Nokia |
| R2-2501049 |
Discussion on NW side data collection |
CMCC |
| R2-2501121 |
Discussion on NW side data collection for positioning |
TCL |
| R2-2501137 |
Further discussion on NW side data collection |
Continental Automotive |
| R2-2501152 |
Discussion on NW-side Data Collection |
SHARP Corporation |
| R2-2501219 |
Discussion on Data Collection for NW-side Model Training |
Futurewei Technologies |
| R2-2501271 |
Enhancements to NW Side Data Collection |
Rakuten Mobile, Inc |
| R2-2501286 |
NW-side data collection for beam management and positioning |
Ericsson |
| R2-2501330 |
Report on [POST128][019][AI PHY] NW side data collection (Nokia) |
Nokia |
| 8.1.4 |
UE side data collection |
|
| R2-2500127 |
Discussion on UE side data collection |
vivo |
| R2-2500142 |
Discussion on UE side data collection |
LG Electronics |
| R2-2500155 |
UE Side Data Collection |
OPPO |
| R2-2500241 |
Consideration on UE side data collection |
CATT |
| R2-2500262 |
Further discussion on UE-side data collection |
Apple |
| R2-2500295 |
Analysis of solutions for UE side model data collection |
NEC |
| R2-2500322 |
Further Discussion on UE-side Data Collection |
MediaTek Inc. |
| R2-2500393 |
On UE Side Data Collection |
Qualcomm Incorporated |
| R2-2500405 |
UE side data collection |
Interdigital Inc. |
| R2-2500471 |
Discussion on Data Collection via UP Tunnel for UE-sided model |
Fujitsu |
| R2-2500799 |
Discussion on UE side data collection |
Xiaomi |
| R2-2500837 |
Further Considerations on UE Side Data Collection |
ZTE Corporation |
| R2-2500889 |
UE side data collection |
Nokia |
| R2-2500911 |
UE side data collection |
Samsung R&D Institute UK |
| R2-2501050 |
Discussion on UE side data collection |
CMCC,China Telecom |
| R2-2501110 |
Discussion on UE-sided data collection for training |
Huawei, HiSilicon |
| R2-2501228 |
Discussion on Data Collection for UE-side Model Training |
Futurewei Technologies |
| R2-2501278 |
Discussion on UE Side data collection |
Rakuten Mobile, Inc |
| R2-2501287 |
Remaining issues on UE-side data collection |
Ericsson |
| 8.1.5 |
Model transfer/delivery |
|
| R2-2500128 |
Discussion on signaling feasibility of dataset and parameter |
vivo |
| R2-2500156 |
Open Discussion on Two Sided Model |
OPPO |
| R2-2500242 |
Signalling feasibility of AIML model transfer |
CATT |
| R2-2500263 |
Discussion on parameters/model transfer in two-sided model |
Apple |
| R2-2500265 |
Feasibility analysis of model/dataset transfer solutions |
Xiaomi |
| R2-2500296 |
Signalling feasibility of dataset and parameter sharing |
NEC |
| R2-2500323 |
Feasibility Analysis on RAN1 Identified Solution for Two-sided Model |
MediaTek Inc. |
| R2-2500394 |
Discussion on Dataset and Parameter Sharing from the Network to the UE for Two-Sided Model Training |
Qualcomm Incorporated |
| R2-2500614 |
Analysis on dataset and parameter transfer for two-sided model |
Lenovo |
| R2-2500836 |
On Evaluation of Standardized Signaling for Two-side model |
ZTE Corporation |
| R2-2500910 |
Discussion on signalling feasibility of dataset and parameter sharing for CSI compression |
Samsung R&D Institute UK |
| R2-2500949 |
Requirements for Model Transfer/Delivery |
T-Mobile USA Inc., Boost Mobile Network, Deutsche Telekom, Orange, Charter Communication, Nokia Corporation |
| R2-2500998 |
Discussion on RAN1 LS on Dataset and Parameter Transfer |
Nokia |
| R2-2501051 |
Discussion on AIML model transfer delivery |
CMCC,China Unicom,China Telecom,CATT,ZTE,Apple,Samsung |
| R2-2501111 |
Discussion on signalling feasibility of dataset and parameter sharing for CSI compression |
Huawei, HiSilicon |
| R2-2501215 |
Discussion on model transfer/delivery |
NTT DOCOMO, INC. |
| R2-2501288 |
On signalling feasibility of dataset and parameter sharing |
Ericsson |
| 8.2.1 |
Organizational |
|
| R2-2500030 |
LS on RAN3 outcome of Ambient IoT study (R3-247923; contact: Huawei) |
RAN3 |
| R2-2500052 |
LS on A-IoT Conclusions in SA WG2 (S2-2413035; contact: Huawei) |
SA2 |
| R2-2500063 |
Reply LS on Assistance Information from CN to the Reader (S2-2501241; contact: ZTE |
SA2 |
| R2-2501027 |
Ambient IoT Work Item work plan |
CMCC, Huawei, T-Mobile USA |
| R2-2501502 |
Reply LS on security aspects of Ambient IoT (S3-251055; contact: OPPO) |
SA3 |
| 8.2.2 |
A-IoT Paging |
|
| R2-2500088 |
Discussion on ambient IoT paging |
LG Electronics Inc. |
| R2-2500129 |
Discussion on AIoT Paging |
vivo |
| R2-2500163 |
Discussion on paging procedure of A-IoT |
Spreadtrum, UNISOC |
| R2-2500212 |
A-IoT paging |
Huawei, HiSilicon |
| R2-2500255 |
Discussion on A-IOT paging procedure |
Xiaomi |
| R2-2500270 |
Discussion on Paging for Ambient IoT |
CATT |
| R2-2500305 |
Discussions on AIoT paging |
Samsung |
| R2-2500414 |
Discussion on Ambient IoT paging message design |
ASUSTeK |
| R2-2500425 |
Discussion on Ambient IoT Paging |
Apple |
| R2-2500452 |
Discussion on paging procedure for Ambient IoT |
OPPO |
| R2-2500472 |
Discussions on AIoT paging |
Fujitsu |
| R2-2500493 |
Paging Aspects for Ambient IOT |
InterDigital |
| R2-2500505 |
Ambient-IoT Paging |
NEC |
| R2-2500610 |
Discussion on paging procedure for Ambient IoT |
Lenovo |
| R2-2500642 |
Discussion on A-IoT paging |
HONOR |
| R2-2500660 |
Discussion on A-IoT paging message |
Tejas Network Limited |
| R2-2500676 |
Discussion on A-IoT paging |
Panasonic |
| R2-2500716 |
Paging design for Ambient IoT |
Nokia |
| R2-2500738 |
Considerations on paging for Ambient IoT |
Sony |
| R2-2500757 |
Discussion on Paging for A-IoT |
Transsion Holdings |
| R2-2500777 |
Paging procedure for A-IoT |
ZTE Corporation, Sanechips |
| R2-2500954 |
Ambient IoT Paging |
Qualcomm Incorporated |
| R2-2501000 |
Discussion on AIoT paging message |
NTT DOCOMO, INC. |
| R2-2501028 |
Discussion on A-IoT paging |
CMCC |
| R2-2501064 |
Discussion on Ambient IoT Paging |
ETRI |
| R2-2501067 |
Discussion on Ambient IoT Paging Procedure |
China Telecom |
| R2-2501069 |
Discussion on DL messages for Ambient IoT UEs |
Ericsson |
| R2-2501080 |
Consideration of A-IoT paging for Ambient IoT |
Kyocera |
| R2-2501249 |
Discussions on A-IoT Paging |
Futurewei |
| R2-2501264 |
AIOT Paging |
TCL |
| R2-2501316 |
Discussions on ambient IoT paging |
ROBERT BOSCH GmbH |
| R2-2501498 |
Recommendation for R2D triggering for Msg1 resources in A-IoT random procedure |
Huawei |
| 8.2.3 |
A-IoT Random Access |
|
| R2-2500130 |
Random Access Procedure for AIoT Device |
vivo |
| R2-2500164 |
Discussion on A-IoT random access |
Spreadtrum, UNISOC |
| R2-2500176 |
Downselection of ambient IoT random access procedures |
MediaTek Inc. |
| R2-2500254 |
Discussion on access procedure for A-IOT |
Xiaomi |
| R2-2500271 |
Discussion on the Random Access for Ambient IoT |
CATT |
| R2-2500297 |
Random Access for Ambient IoT device |
NEC |
| R2-2500301 |
A-IoT random access procedure |
Huawei, HiSilicon |
| R2-2500375 |
Ambient-IoT Random Access |
Ofinno, LLC |
| R2-2500415 |
Unified solution for Ambient IoT random access type |
ASUSTeK |
| R2-2500426 |
Discussion on Random Access for Ambient IoT |
Apple |
| R2-2500448 |
Considerations for paging re-access on D2R failure |
Panasonic |
| R2-2500455 |
Discussion on random access for A-IoT |
OPPO |
| R2-2500473 |
Discussions on AIoT Random Access |
Fujitsu |
| R2-2500494 |
Random Access Procedure for Ambient IOT |
InterDigital |
| R2-2500572 |
Discussion on random access for A-IoT |
China Telecom |
| R2-2500609 |
Discussion on random access for Ambient IoT |
Lenovo |
| R2-2500643 |
Discussion on A-IoT random access |
HONOR |
| R2-2500661 |
Discussion on A-IoT random access |
Tejas Network Limited |
| R2-2500714 |
Signalling design for random access |
Nokia |
| R2-2500758 |
Discussion on Random Access for A-IoT |
Transsion Holdings |
| R2-2500778 |
Random access procedure for A-IoT |
ZTE Corporation, Sanechips |
| R2-2500863 |
Discussion on UL multiple access |
Ericsson |
| R2-2501013 |
Further consideration on A-IoT random access |
CMCC |
| R2-2501081 |
Consideration of A-IoT random access for Ambient IoT |
Kyocera |
| R2-2501126 |
Views on Random Access Aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2501128 |
Discussion on random access aspects for Ambient IoT |
LG Electronics Inc. |
| R2-2501142 |
Discussion on AIoT random access procedure |
NTT DOCOMO, INC. |
| R2-2501145 |
Discussion on random access for ambient IoT |
Google Ireland Limited |
| R2-2501266 |
Discussion on unified CBRA procedures for Ambient IoT |
Samsung |
| 8.2.4 |
A-IoT Data Transmission and Other general aspects |
|
| R2-2500131 |
AIoT Data Transmission |
vivo |
| R2-2500165 |
Discussion on A-IoT data transmission |
Spreadtrum, UNISOC |
| R2-2500177 |
Ambient IoT AS id management and relation to energy status indication |
MediaTek Inc. |
| R2-2500178 |
Ambient IoT segmentation (both directions) |
MediaTek Inc. |
| R2-2500213 |
A-IoT data transmission and general aspects |
Huawei, HiSilicon |
| R2-2500253 |
Protocol design principle and considerations on Data transmission |
Xiaomi |
| R2-2500272 |
Discussion on the A-IoT Data Transmission and Other General Aspects |
CATT |
| R2-2500306 |
Discussion on A-IoT data transmission |
Samsung |
| R2-2500387 |
Discussion on A-IoT data transmission and other general aspects |
Lenovo |
| R2-2500454 |
Discussion on AIoT data transmission related functionalities |
OPPO |
| R2-2500474 |
Discussions on Data Transmission and Other General Aspects |
Fujitsu |
| R2-2500495 |
Data Transmission and General Aspects for Ambient IOT |
InterDigital |
| R2-2500499 |
Discussion on A-IoT data segmentation and transmission |
KT Corp. |
| R2-2500557 |
Ambient IoT MAC design for UL and DL data transmission |
Apple |
| R2-2500573 |
Considerations on A-IoT data transmission and other general aspects |
China Telecom |
| R2-2500644 |
Discussion on Data Transmission for Ambient IoT |
HONOR |
| R2-2500672 |
Discussion on AS ID, segmentation and control signaling format |
Panasonic |
| R2-2500732 |
Ambient-IoT Data transmission |
NEC Corporation |
| R2-2500739 |
Considerations on segmentation |
Sony |
| R2-2500779 |
MAC layer design and other aspects for A-IoT |
ZTE Corporation, Sanechips |
| R2-2500821 |
Discussion on AS ID |
Continental Automotive |
| R2-2500920 |
Discussion on AIoT general aspects |
NTT DOCOMO, INC. |
| R2-2500951 |
Discussion on data transmission and general aspects |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2500974 |
A-IoT Data Transmission and Other General Aspects |
Ericsson |
| R2-2501030 |
Discussion on functionality for A-IoT |
CMCC |
| R2-2501082 |
Consideration of A-IoT data transmission for Ambient IoT |
Kyocera |
| R2-2501127 |
Data Transmission and Other General Aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2501138 |
Discussion on A-IoT data transmission |
LG Electronics Inc. |
| R2-2501178 |
Discussion on AS ID for ambient IoT |
Google Ireland Limited |
| R2-2501232 |
AIoT General Aspects |
Nokia |
| R2-2501250 |
Discussions on A-IoT data transmission and other aspects |
Futurewei |
| R2-2501510 |
[AT129][020][AIoT] AS ID (XiaomiHuawei) |
Xiaomi, Huawei |
| R2-2501514 |
Offline report for segment retransmission |
ZTE Corporation (rapporteur) |
| 8.3.1 |
Organizational |
|
| R2-2500287 |
Text proposal of 38.744 |
OPPO |
| R2-2500288 |
Discussion on work plan of AI mobility SI |
OPPO,MediaTek,Nokia,Interdigital |
| 8.3.2.1 |
Simulation results |
|
| R2-2500161 |
Simulation results on RRM measurement prediction |
Spreadtrum, UNISOC, BUPT |
| R2-2500167 |
Discussion on RRM measurement predictions and prediction-based mobility events |
Sharp |
| R2-2500214 |
Simulation results of RRM measurement prediction |
vivo |
| R2-2500290 |
Analysis on simulation results of RRM measurement prediction |
OPPO |
| R2-2500313 |
Discussions on simulation results of the RRM measurement prediction |
NTT DOCOMO, INC. |
| R2-2500324 |
Simulation result for RRM prediction and system level simulation |
MediaTek Inc. |
| R2-2500406 |
Simulation results for RRM measurement predictions |
Interdigital Inc. |
| R2-2500520 |
Simulation results for RRM measurement prediction |
China Telecom Corporation Ltd. |
| R2-2500639 |
Discussion on simulation results for RRM measurement prediction |
Samsung |
| R2-2500852 |
Simulation results for spatial domain RRM measurement predictions |
Ericsson |
| R2-2500890 |
Additional simulation results for RRM measurement prediction |
Huawei, HiSilicon |
| R2-2500899 |
Discussion on RRM measurement prediction |
ZTE Corporation |
| R2-2500946 |
Simulation results for RRM measurement predictions |
Nokia |
| R2-2501040 |
Potential specification impact for RRM measurement prediction |
CMCC |
| R2-2501497 |
[POST128][021][AI Mob] Templates for simulations (Mediatek/OPPO) |
Mediatek Inc., OPPO |
| R2-2501557 |
[AT129][022][AI Mob] Simulations (Mediatek) |
Mediatek Inc. |
| 8.3.2.2 |
Model Generalization |
|
| R2-2500215 |
Simulation results of model generalization for RRM measurement prediction |
vivo |
| R2-2500243 |
Simulation results of Model Generalization |
CATT, Turkcell |
| R2-2500289 |
Discussion on model generalization of RRM measurement prediction |
OPPO |
| R2-2500314 |
Discussions on generalization of RRM measurement prediction |
NTT DOCOMO, INC. |
| R2-2500318 |
Model Generalization for AIML RRM Prediction |
MediaTek Inc. |
| R2-2500407 |
Generalization of AIML models for RRM measurement prediction |
Interdigital Inc. |
| R2-2500542 |
Discussion on Generalization Issues for AI/ML Mobility |
Samsung |
| R2-2500559 |
Email discussion summary for [Post128][018][AI Mob] generalization (Apple) |
Apple |
| R2-2500601 |
Simulation results on Model Generalization for RRM measurement prediction |
Spreadtrum, UNISOC, BUPT |
| R2-2500800 |
Discussion on generalization performance over UE speed of GC1 |
Xiaomi |
| R2-2500801 |
Discussion on generalization performance over UE speed of GC2 |
Xiaomi |
| R2-2500851 |
Generalization of the AI/ML models for RRM prediction |
Ericsson |
| R2-2500891 |
Model generalization evaluation for RRM measurement prediction |
Huawei, HiSilicon |
| R2-2500900 |
Discussion on model generalization of RRM measurement prediction |
ZTE Corporation |
| R2-2500948 |
Generalization of ML mobility use-cases |
Nokia, Nokia Shanghai Bell |
| R2-2501052 |
Discussion on model generalization |
CMCC |
| R2-2501071 |
Simulation Results for Model Generalization |
Qualcomm Incorporated |
| R2-2501459 |
Simulation Results for Model Generalization |
Qualcomm Incorporated |
| 8.3.3 |
Measurement event predictions |
|
| R2-2500216 |
Simulation results of measurement event prediction and SLS |
vivo |
| R2-2500244 |
Simulation results of event A3 prediction |
CATT, Turkcell |
| R2-2500245 |
Simulation results of AI based Handover performance |
CATT, Turkcell |
| R2-2500291 |
Discussion on simulation results of measurement event prediction |
OPPO |
| R2-2500299 |
Simulation assumption for Measurement event prediction |
NEC |
| R2-2500315 |
Discussions on measurement event prediction |
NTT DOCOMO, INC. |
| R2-2500319 |
Preliminary results of indirect prediction and simulation assumption for direct prediction |
MediaTek Inc. |
| R2-2500399 |
Simulation results for measurement event prediction |
Xiaomi |
| R2-2500408 |
Measurement event predictions |
Interdigital Inc. |
| R2-2500560 |
On measurement event prediction |
Apple |
| R2-2500640 |
Simulation results for measurement event prediction and system level performance |
Samsung |
| R2-2500892 |
Simulation results for measurement event prediction |
Huawei, HiSilicon |
| R2-2500919 |
Evaluation of measurement event prediction |
Ericsson |
| R2-2500947 |
On the measurement event prediction |
Nokia |
| R2-2501041 |
Simulation results for Measurement event predictions |
CMCC |
| R2-2501070 |
Measurement Event prediction and handover modelling |
Qualcomm Incorporated |
| R2-2501072 |
Simulation Results for Measurement Event Predictions |
Qualcomm Incorporated |
| R2-2501241 |
Discussion on system level simulation |
ETRI |
| R2-2501293 |
Discussion on measurement event prediction |
ZTE Corporation |
| R2-2501499 |
Simulation Results for Measurement Event Predictions |
Qualcomm Incorporated |
| R2-2501555 |
Summary of [AT129][027][AI Mob] Simulation methodology (OPPO) |
OPPO |
| 8.3.4 |
RLF/HO failure prediction |
|
| R2-2500327 |
AI-ML based RLF/HO failure prediction |
Rakuten Mobile, Inc |
| R2-2500734 |
Discussion on simulation metric for RLF prediction |
KDDI Corporation |
| 8.4.1 |
Organizational |
|
| R2-2501092 |
Introduction of LP-WUS/LP-WUR |
Ericsson |
| 8.4.2 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
|
| R2-2500050 |
LS Reply on LP-WUS subgrouping (S2-2412876; contact: Huawei) |
SA2 |
| R2-2500135 |
Discussion of LR and MR operating in same/different frequency band |
MediaTek Inc. |
| R2-2500143 |
General considerations on the procedure for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2500150 |
LR and MR operating frequencies |
Vodafone, Huawei, HiSilicon,Vivo |
| R2-2500158 |
Discussion on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Huawei, HiSilicon |
| R2-2500246 |
LP-WUS in RRC_IDLE/INACTIVE |
CATT |
| R2-2500282 |
Discussion on LP-WUS in RRC_IDLE/INACTIVE |
NEC |
| R2-2500302 |
Discussion on SA2 LS on LP-WUS subgrouping |
Huawei, HiSilicon |
| R2-2500343 |
Discussion on LP-WUS WUR in RRC_IDLE INACTIVE |
vivo |
| R2-2500456 |
Discussion on LP-WUS procedure and configuration |
OPPO |
| R2-2500589 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Apple |
| R2-2500645 |
Discussion on LP-WUS in RRC_IDLE/INACTIVE |
HONOR |
| R2-2500663 |
On Idle/Inactive mode procedures for LP-WUS |
Tejas Network Limited |
| R2-2500740 |
RAN2 aspects on LP-WUS/WUR in RRC Idle/Inactive mode |
Sony |
| R2-2500857 |
Procedure and Configuration of LP-WUS in RRC IDLE/INACTIVE |
Lenovo |
| R2-2500868 |
LP-WUS operation in RRC_IDLE and RRC_INACTIVE |
LG Electronics Inc. |
| R2-2500943 |
Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes |
InterDigital, Inc. |
| R2-2500993 |
LP-WUS in IDLE and INACTIVE |
Nokia |
| R2-2501002 |
Discussion on the LP-WUS handling for Emergency call back |
NTT DOCOMO INC.. |
| R2-2501006 |
Discussion on RRC CONNECTION load balancing for LP-WUS capable UEs |
NTT DOCOMO INC.. |
| R2-2501017 |
Further considerations on LP-WUS operation in IDLE INACTIVE mode |
CMCC |
| R2-2501075 |
Discussion on LP-WUS in RRC_IDLE and RRC_INACTIVE |
Sharp |
| R2-2501089 |
Procedure and configuration of LP-WUS for IDLE and INACTIVE mode |
ZTE Corporation, Sanechips |
| R2-2501093 |
LP-WUS in Idle and Inactive |
Ericsson |
| R2-2501132 |
Procedure and Configuration of LP-WUS in RRC Idle Inactive Mode |
Samsung |
| R2-2501252 |
LP-WUS operation in IDLE/Inactive state |
Qualcomm Incorporated |
| R2-2501388 |
Reply LS on LP-WUS subgrouping |
RAN2 |
| R2-2501394 |
Reply LS on LP-WUS operation in IDLE/INACTIVE mode |
RAN2 |
| R2-2501443 |
Discussion report on [AT129][203][LPWUS] |
vivo |
| 8.4.3 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
|
| R2-2500144 |
Discussion on RRM measurement relaxation for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2500201 |
Further discussion on the criteria for RRM measurement relaxation and offloading |
Huawei, HiSilicon |
| R2-2500247 |
RRM Relaxation and Offloading in RRC_IDLE/INACTIVE |
CATT |
| R2-2500283 |
Discussion on LP-WUS RRM relaxation and offloading |
NEC |
| R2-2500344 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
vivo |
| R2-2500457 |
Discussion on RRM measurement in RRC IDLE and INACTIVE |
OPPO |
| R2-2500590 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Apple |
| R2-2500608 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Lenovo |
| R2-2500869 |
RRM relaxation and RRM offloading |
LG Electronics Inc. |
| R2-2500944 |
Discussion on RRM measurement relaxation and offloading |
InterDigital, Inc. |
| R2-2500994 |
RRM measurement relaxation in RRC_IDLE/INACTIVE |
Nokia |
| R2-2501043 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE INACTIVE |
CMCC |
| R2-2501068 |
Discussion on RRM measurement relaxation and offloading for RRC_IDLE/INACTIVE |
China Telecom |
| R2-2501076 |
Discussion on RRM measurement relaxation and offloading |
Sharp |
| R2-2501090 |
RRM measurement relaxation and offloading in RRC_IDLE and RRC_INACTIVE mode |
ZTE Corporation, Sanechips |
| R2-2501094 |
LP-WUS and RRM measurements |
Ericsson |
| R2-2501131 |
Discussion on neighboring cell measurement with LR |
InterDigital, Ericsson, Nokia, Sony, Vodafone |
| R2-2501133 |
RRM measurement relaxation and offloading in RRC Idle Inactive Mode |
Samsung |
| R2-2501254 |
LP-WUS RRM measurement relaxation and offloading |
Qualcomm Incorporated |
| 8.4.4 |
Procedures for LP-WUS in RRC_CONNECTED |
|
| R2-2500012 |
LS on LP-WUS operation in CONNECTED mode (R1-2410909; contact: NTT DOCOMO) |
RAN1 |
| R2-2500074 |
Discussing on LP-WUS monitoring in Connected mode |
Xiaomi |
| R2-2500248 |
Analysis on LP-WUS for RRC_CONNECTED |
CATT |
| R2-2500284 |
Discussion on LP-WUS in RRC_CONNECTED |
NEC |
| R2-2500303 |
Further discussion on LP-WUS for RRC_CONNECTED mode |
Huawei, HiSilicon |
| R2-2500345 |
Discussion on LP-WUS WUR in RRC_Connected |
vivo |
| R2-2500458 |
Discussion on LP-WUS in RRC_CONNECTED |
OPPO |
| R2-2500591 |
Procedures for LP-WUS in RRC_CONNECTED |
Apple |
| R2-2500666 |
LP-WUS operation in Connected mode |
Tejas Network Limited |
| R2-2500717 |
LP-WUS in CONNECTED mode |
InterDigital |
| R2-2500741 |
Considerations on LP-WUS/WUR in RRC Connected mode |
Sony |
| R2-2500827 |
Discussion on LP-WUS in RRC_CONNECTED |
LG Electronics Inc. |
| R2-2500860 |
LP-WUS in RRC Connected Mode |
Lenovo |
| R2-2501003 |
Discussion on the LS from RAN1 on LP-WUS CONNECTED |
NTT DOCOMO INC.. |
| R2-2501018 |
Discussion on LP-WUS operation in CONNECTED mode |
CMCC |
| R2-2501077 |
Discussion on LP-WUS in RRC_CONNECTED |
Sharp |
| R2-2501091 |
Procedures for LP-WUS in RRC_CONNECTED |
ZTE Corporation, Sanechips |
| R2-2501095 |
LP-WUS in Connected |
Ericsson |
| R2-2501134 |
Procedures for LP-WUS in RRC Connected Mode |
Samsung |
| R2-2501201 |
LP-WUS in RRC_CONNECTED |
Nokia, Nokia Shanghai Bell |
| R2-2501253 |
LP-WUS operation in CONNECTED state |
Qualcomm Incorporated |
| R2-2501326 |
Analysis on LP-WUS for RRC_CONNECTED |
CATT |
| R2-2501395 |
Reply LS on LP-WUS operation in CONNECTED mode |
RAN2 |
| R2-2501444 |
[AT129][204][LPWUS] Proposals for reply to R1 LS R2-2500012/R1-2410909 (CATT) |
CATT |
| 8.5.1 |
Organizational |
|
| R2-2500014 |
Reply LS on SSB relation in On-demand SSB and SSB adaptation on Scell (R1-2410917; contact: Ericsson) |
RAN1 |
| R2-2501245 |
Running RRC CR for enhancements for network energy efficiency |
Ericsson |
| 8.5.2 |
On-demand SSB SCell operation |
|
| R2-2500075 |
Discussion on on-demand SSB |
Xiaomi |
| R2-2500115 |
Discussion on On-Demand SSB |
OPPO |
| R2-2500171 |
On-demand SSB SCell Operation |
Samsung |
| R2-2500211 |
Discussion on OD-SSB |
Rakuten Mobile, Inc |
| R2-2500225 |
Consideration on on-demand SSB SCell operation |
CATT |
| R2-2500256 |
Discussion on on-demand SSB for Scell |
Apple |
| R2-2500334 |
Remaining issues of on-demand SSB SCell operation |
vivo |
| R2-2500398 |
Discussion on on-demand SSB SCell operation |
Sharp |
| R2-2500502 |
Further discussion on On-demand SSB for SCell |
NEC |
| R2-2500518 |
Discussion on on-demand SSB SCell operation |
Fujitsu |
| R2-2500551 |
On demand SSB handling |
Nokia, Nokia Shanghai Bell |
| R2-2500626 |
Issues on the procedure of on-demand SSB SCell operation |
Lenovo |
| R2-2500646 |
Discussion on on-demand SSB configuration |
HONOR |
| R2-2500670 |
On-demand SSB SCell operation |
Panasonic |
| R2-2500691 |
Discussion on on-demand SSB SCell operation for NES |
Huawei, HiSilicon |
| R2-2500731 |
Discussion on on-demand SSB for NES |
Ericsson |
| R2-2500742 |
On-demand SSB Scell operation discussion |
Sony |
| R2-2500791 |
On demand SSB transmission for SCell |
InterDigital |
| R2-2500870 |
On-demand SSB SCell operation |
LG Electronics Inc. |
| R2-2501019 |
Discussion on On-demand SSB for Scell |
CMCC |
| R2-2501059 |
Discussion on on-demand SSB SCell operation |
NTT DOCOMO, INC. |
| R2-2501086 |
Remaining issues of on demand SSB Scell operation |
ZTE Corporation, Sanechips |
| R2-2501162 |
Discussion on On-demand SSB SCell Operation |
Qualcomm Incorporated |
| R2-2501317 |
Discussion on On-demand SSB SCell Operation |
Qualcomm Incorporated |
| 8.5.3 |
On-demand SIB1 |
|
| R2-2500170 |
On-demand SIB1 |
Samsung |
| R2-2500190 |
Discussion on on-demand SIB1 |
Xiaomi |
| R2-2500226 |
Consideration on on-demand SIB1 |
CATT |
| R2-2500257 |
Remaining issues on on-demand SIB1 |
Apple |
| R2-2500280 |
Discussion on on-demand SIB1 for NES |
Rakuten Mobile, Inc |
| R2-2500335 |
Discussion on OD-SIB1 for RRC IDLE and INACTIVE UE |
vivo |
| R2-2500341 |
Discussion on on-demand SIB1 operation for NES |
Huawei, HiSilicon |
| R2-2500396 |
On-demand SIB1 WUS provisioning and UE behaviour |
NEC. |
| R2-2500449 |
Discussion on Ondemand-SIB1 |
KDDI Corporation |
| R2-2500463 |
Discussion on the support for OD-SIB1 |
Google |
| R2-2500519 |
Discussion on on-demand SIB1 procedure for NES |
Fujitsu |
| R2-2500552 |
On demand SIB1 handling |
Nokia, Nokia Shanghai Bell |
| R2-2500647 |
Discussion on on-demand SIB1 |
HONOR |
| R2-2500671 |
RAN Plenary outcome and other remaining issues |
Lenovo |
| R2-2500729 |
Discussion on on-demand SIB1 for NES |
Ericsson |
| R2-2500735 |
Consideration on on-demand SIB1 |
OPPO |
| R2-2500743 |
Remaining details for on-demand SIB1 |
Sony |
| R2-2500789 |
On-demand SIB1 request and reception |
InterDigital |
| R2-2500871 |
On-demand transmission of SIB1 |
LG Electronics Inc. |
| R2-2500921 |
Views on On-demand SIB1 operation for idle/inactive UEs |
Vodafone |
| R2-2501008 |
Discussion on handling RLF in a NES cell |
ITRI |
| R2-2501020 |
Discussion on On-demand SIB1 |
CMCC |
| R2-2501061 |
Discussion on on-demand SIB1 |
NTT DOCOMO, INC. |
| R2-2501087 |
Remaining issues of on demand SIB1 |
ZTE Corporation, Sanechips |
| R2-2501157 |
Discussion on on-demand SIB1 |
Jio |
| R2-2501163 |
Discussion on On-demand SIB1 |
Qualcomm Incorporated |
| R2-2501192 |
Discussion on remaining details of on-demand SIB1 |
SHARP Corporation |
| R2-2501216 |
On-demand SIB1 for Idle/Inactive mode UEs |
III |
| R2-2501270 |
Discussion on On-demand SIB1 for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2501465 |
Summary report of [AT129][105][NES] (Apple) |
Apple |
| 8.5.4 |
Adaptation of common signal/channel transmissions |
|
| R2-2500076 |
Discussion on common signal adaptation |
Xiaomi |
| R2-2500149 |
Discussion on common signal and channel adaptation |
LG Electronics Inc. |
| R2-2500172 |
Adaptation of common signal channel transmissions |
Samsung |
| R2-2500199 |
Discussion on adaptation of common signal channel transmission |
OPPO |
| R2-2500227 |
Adaptation of Common signal channel transmissions |
CATT |
| R2-2500258 |
Discussion on common signal transmission adaptation |
Apple |
| R2-2500336 |
Discussion on adaptation of common signal transmissions |
vivo |
| R2-2500397 |
PRACH and paging adaptation for NES |
NEC |
| R2-2500416 |
Discussion on PRACH adaptation |
ASUSTeK |
| R2-2500475 |
Adaptation of common signal or channel |
Fujitsu |
| R2-2500553 |
Adaptation of common signals |
Nokia, Nokia Shanghai Bell |
| R2-2500627 |
Paging and PRACH adaptation |
Lenovo |
| R2-2500692 |
Discussion on adaptation of common signals/channels transmissions |
Huawei, HiSilicon |
| R2-2500744 |
RAN2 impacts on SSB and RACH adaptations |
Sony |
| R2-2500790 |
Time domain adaptation of common signalling and channels |
InterDigital |
| R2-2501021 |
Discussion on common signalling adaptation |
CMCC |
| R2-2501062 |
Discussion on adaptation of common signal and channel |
NTT DOCOMO, INC. |
| R2-2501065 |
Adaptation of common signal/channel transmissions for NES |
Ericsson |
| R2-2501088 |
Common signal/channel adaption |
ZTE Corporation, Sanechips |
| R2-2501165 |
Discussion on Adaptation of Common Signal/Channel Transmissions |
Qualcomm Incorporated |
| R2-2501231 |
Discussion on RACH adaptation |
SHARP Corporation |
| R2-2501483 |
LS on paging enhancement in R19 NES |
RAN2 |
| R2-2501484 |
Reply LS on SSB adaptation |
RAN2 |
| 8.6.1 |
Organizational |
|
| R2-2500029 |
Reply LS for LS on the support of semi-persistent CSI-RS resource for LTM candidate cells (R3-247911; contact: CATT) |
RAN3 |
| R2-2500224 |
UE capability of NR mobility enhancements |
CATT |
| R2-2500563 |
Introduction of NR mobility enhancements Phase 4 in TS 37.340 |
China Telecom |
| R2-2500805 |
Draft running RRC CR for event-triggered meas report |
Huawei, HiSilicon |
| R2-2500887 |
Introduction of NR mobility enhancements Phase 4 in TS 38.300 |
Apple |
| R2-2500991 |
List of FFSs for LTM and CLTM |
Ericsson |
| R2-2500992 |
Running RRC CR for inter-CU and conditional LTM |
Ericsson |
| R2-2501203 |
Running MAC CR for Mob Ph4 |
vivo (Rapporteur) |
| R2-2501471 |
Summary of [AT129][112][MOB] inter-CU and CLTM |
Ericsson |
| R2-2501473 |
Discussion report on [AT129][113][MOB] MAC open issues (vivo) |
vivo |
| 8.6.2 |
Inter-CU LTM |
|
| R2-2500132 |
Leftover issues on Inter-CU LTM |
MediaTek Inc. |
| R2-2500136 |
Discussion on remaining issues of inter-CU LTM |
LG Electronics Inc. |
| R2-2500147 |
Remaining issues on inter-CU LTM in DC cases |
Fujitsu |
| R2-2500207 |
Discussion on open issues for inter-CU LTM |
OPPO |
| R2-2500221 |
Discussion on Inter-CU LTM |
CATT |
| R2-2500304 |
Further Considerations to Support Inter-CU LTM |
Samsung |
| R2-2500326 |
Discussion on Inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2500346 |
Discussion on inter-CU LTM |
vivo |
| R2-2500423 |
Discussion on inter-CU LTM |
Xiaomi |
| R2-2500442 |
Discussion on inter-CU LTM |
ZTE Corporation, Sanechips |
| R2-2500504 |
Discussion on inter-CU LTM |
NEC |
| R2-2500564 |
Discussion on inter-CU LTM |
China Telecom |
| R2-2500581 |
Remaining issues in Inter-CU LTM |
Apple |
| R2-2500630 |
Some issues for Inter-CU LTM |
Lenovo |
| R2-2500648 |
Further discussion on inter-CU LTM |
HONOR |
| R2-2500667 |
Discussion on remaining FFSs for inter-CU LTM |
Ericsson |
| R2-2500745 |
LTM for Inter-CU |
Sony |
| R2-2500759 |
Further discussion on supporting inter-CU LTM cell switch |
Transsion Holdings |
| R2-2500795 |
Further analysis on Inter-CU LTM open issue |
Nokia |
| R2-2500964 |
Inter-CU LTM |
Huawei, HiSilicon |
| R2-2501009 |
Reference configuration for inter-CU LTM |
ITRI |
| R2-2501022 |
Discussion on Inter-CU LTM |
CMCC |
| R2-2501193 |
Discussion on issues for supporting inter-CU LTM |
Sharp |
| R2-2501296 |
Discussion on inter-CU LTM |
DENSO CORPORATION |
| 8.6.3 |
L1 event triggered measurement reporting |
|
| R2-2500133 |
Remaining issues on event triggered L1 MR |
MediaTek Inc. |
| R2-2500208 |
Open issues for event triggered L1 measurement reporting |
OPPO |
| R2-2500222 |
L1 event triggered measurement reporting |
CATT |
| R2-2500328 |
Discussion on L1 event triggered measurement reporting |
Rakuten Mobile, Inc |
| R2-2500332 |
Further View on L1 Measurement Reporting Enhancements for Rel-19 LTM |
Nokia |
| R2-2500347 |
Discussion on LTM measurement event evaluation and reporting |
vivo |
| R2-2500373 |
Discussion on event triggered LTM report |
Ofinno, LLC |
| R2-2500400 |
Remaining issues of L1 event triggered measurement reporting |
Xiaomi |
| R2-2500417 |
Discussion on MR MAC CE for LTM |
ASUSTeK |
| R2-2500443 |
Discussion on L1 event triggered MR |
ZTE Corporation, Sanechips |
| R2-2500476 |
Discussions on event triggered L1 measurement reporting |
Fujitsu |
| R2-2500485 |
L1 event-triggered measurement reporting for LTM |
Qualcomm Incorporated |
| R2-2500503 |
MAC CE for L1 event triggered measurement report |
NEC |
| R2-2500565 |
Discussion on L1 event triggered measurement reporting |
China Telecom |
| R2-2500592 |
LTM event triggered measurement reporting |
Apple |
| R2-2500631 |
Event based L1 measurement report |
Lenovo |
| R2-2500649 |
Discussion on measurement event evaluation and report |
HONOR |
| R2-2500668 |
Discussions on event-based L1 measurements |
Ericsson |
| R2-2500760 |
Discussion on L1 event triggered measurement reporting |
Transsion Holdings |
| R2-2500803 |
Discussion on event-triggered meas report |
Huawei, HiSilicon |
| R2-2500804 |
Summary of [POST128][108][MOB] RRC running CR (Huawei) |
Huawei, HiSilicon |
| R2-2500874 |
L1 event-triggered measurement reporting for LTM |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2500878 |
Event triggered L1 measurement reporting for LTM. |
Interdigital, Inc. |
| R2-2500955 |
L1 measurement event configuration and reporting |
Panasonic |
| R2-2501042 |
Discussion on L1 event triggered measurement reporting |
CMCC |
| R2-2501083 |
Further details of event-triggered L1 measurement reporting for LTM |
Kyocera |
| R2-2501168 |
Remaining Issues of L1 Event Triggered Measurement Report |
Samsung |
| R2-2501186 |
Event triggered LTM report |
LG Electronics Inc. |
| R2-2501194 |
Discussion on issues for supporting L1 event triggered measurement reporting |
Sharp |
| R2-2501204 |
Summary of [POST128][109][MOB] Open issues (vivo) |
vivo (Rapporteur) |
| R2-2501328 |
Discussion on event-triggered meas report |
Huawei, HiSilicon |
| R2-2501485 |
LS on number of beam measurements in the measurement report MAC CE |
RAN2 |
| R2-2501553 |
Summary of [AT129][MOB] L1 measurements, enter and leave condition |
Ericsson |
| 8.6.4 |
Conditional intra-CU LTM |
|
| R2-2500134 |
Further discussion on Conditional LTM |
MediaTek Inc. |
| R2-2500137 |
Discussion on remaining issues of CLTM |
LG Electronics Inc. |
| R2-2500168 |
Discussion on Conditional intra-CU LTM |
Baicells |
| R2-2500209 |
Discussion on conditional LTM |
OPPO |
| R2-2500223 |
Discussion on Conditional Intra-CU LTM |
CATT |
| R2-2500251 |
Discussion on Conditional Intra CU LTM |
Lekha Wireless Solutions |
| R2-2500286 |
Conditional LTM |
Rakuten Mobile, Inc |
| R2-2500348 |
Discussion on conditional LTM |
vivo |
| R2-2500424 |
Discussion on conditional LTM |
Xiaomi |
| R2-2500444 |
Discussion on conditional intra-CU LTM |
ZTE Corporation, Sanechips |
| R2-2500461 |
Discussion on conditional intra-CU LTM |
Panasonic |
| R2-2500477 |
Discussion on conditional Intra-CU LTM |
Fujitsu |
| R2-2500486 |
Conditional intra-CU LTM |
Qualcomm Incorporated |
| R2-2500487 |
Further discussion on conditional LTM |
ETRI |
| R2-2500566 |
Discussion on conditional intra-CU LTM |
China Telecom |
| R2-2500593 |
Conditional Intra-CU LTM |
Apple |
| R2-2500650 |
Discussion on conditional LTM |
HONOR |
| R2-2500669 |
Discussion on DC and remaining FFSs for CLTM |
Ericsson |
| R2-2500673 |
Discussion on conditional intra-CU LTM |
NEC |
| R2-2500761 |
Further discussion on supporting conditional LTM |
Transsion Holdings |
| R2-2500856 |
CLTM Scenarios and remaining points |
Lenovo |
| R2-2500879 |
Conditional LTM. |
Interdigital, Inc. |
| R2-2500945 |
On conditional LTM |
Nokia |
| R2-2500965 |
Intra-CU conditional LTM |
Huawei, HiSilicon |
| R2-2501001 |
Discussion on Conditional Intra-CU LTM |
KDDI Corporation |
| R2-2501023 |
Discussion on Conditional LTM |
CMCC |
| R2-2501073 |
Initial consideration of coexistence scenarios for C-LTM |
Kyocera |
| R2-2501074 |
Discussion on TA validity timer for C-LTM |
Kyocera |
| R2-2501155 |
Discussion on Conditional Intra CU LTM |
Jio Platforms (JPL) |
| R2-2501156 |
Discussion on Conditional intra-CU LTM |
ITL |
| R2-2501169 |
Remaining Issues of Conditional Intra-CU LTM |
Samsung |
| R2-2501195 |
Discussion on issues for supporting conditional LTM |
Sharp |
| R2-2501198 |
Discussion on Conditional intra-CU LTM |
NTT DOCOMO, INC. |
| R2-2501233 |
Discussion on L1 conditions for conditional LTM |
Google Korea LLC |
| 8.7.1 |
Organizational |
|
| R2-2500020 |
Reply LS on multi-modality awareness (R3-247874; contact: Huawei) |
RAN3 |
| R2-2500021 |
Reply LS to SA2 for PDU Set Information Marking Support without QoS parameters (R3-247875; contact: ZTE) |
RAN3 |
| R2-2500037 |
Response LS on gaps/restrictions that are caused by RRM measurements (R4-2420198; contact: Qualcomm) |
RAN4 |
| R2-2500056 |
Reply to LS on appropriate range and granularity of bit rate adaptation for XR applications (S4-242182; contact: Qualcomm) |
SA4 |
| R2-2500057 |
LS Reply on multi-modality awareness (S4-242223; contact: Huawei) |
SA4 |
| R2-2500060 |
LS on multi-modality awareness (SP-241921; contact: CMCC) |
SA |
| R2-2500090 |
Introduction to R19 XR enhancements |
Qualcomm Incorporated |
| R2-2500488 |
Rapporteur Inputs |
Nokia, Qualcomm (Rapporteurs) |
| R2-2500489 |
Draft Stage 2 CR for XR |
Nokia (Rapporteur) |
| R2-2500808 |
Draft runnnig RRC CR for R19 XR |
Huawei, HiSilicon |
| R2-2501147 |
PDCP running CR for R19 XR |
LG Electronics Inc. (Rapporteur) |
| R2-2501197 |
PDCP running CR for R19 XR |
LG Electronics Inc. (Rapporteur) |
| R2-2501205 |
RLC running CR for XR |
vivo |
| R2-2501246 |
Draft runnnig RRC CR for R19 XR |
Huawei, HiSilicon |
| R2-2501501 |
Reply to LS on Application-Layer FEC Awareness at RAN (S4-250252; contact: Qualcomm) |
SA4 |
| R2-2501508 |
Reply LS on XR UL Rate Control (R3-250805; contact: Meta) |
RAN3 |
| 8.7.3 |
RRM measurement gaps/restrictions related enhancements |
|
| R2-2500091 |
Discussion on measurement gap cancelation |
Qualcomm Incorporated |
| R2-2500099 |
RRM measurement gaps/restrictions related enhancements |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2500182 |
Discussion on Enabling TX/RX for XR during RRM Measurements |
CATT |
| R2-2500196 |
Discussion on Measurement Gap enhancements |
OPPO |
| R2-2500349 |
Discussion on RRM measurement gaps enhancements |
vivo |
| R2-2500377 |
RAN2 impacts of measurement gap enhancements |
Sharp |
| R2-2500478 |
Discussions on measurement gap related enhancements |
Fujitsu |
| R2-2500500 |
RRC-based semi-static MG skipping solution |
NEC Corporation |
| R2-2500651 |
Discussion on RRM Measurement Gaps Enhancements |
HONOR |
| R2-2500678 |
Views on Enhancements Relating to RRM Measurement Gaps |
Apple |
| R2-2500715 |
Enabling TX/RX for XR during measurement gaps/restrictions |
Lenovo |
| R2-2500746 |
Discussion on enabling TX/RX for XR during RRM measurements |
Sony |
| R2-2500764 |
RRM measurement gaps/restrictions related enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2500781 |
Measurement gap skipping for XR |
ZTE Corporation, Sanechips |
| R2-2500793 |
RRM measurement gap related enhancements for XR |
InterDigital |
| R2-2500806 |
Discussion on RRM enhancements for XR |
Huawei, HiSilicon |
| R2-2500824 |
Discussion on enhancement for MG skipping |
LG Electronics Inc. |
| R2-2500839 |
Remaining Issues on RRM Measurement Enhancements |
China Telecom |
| R2-2500862 |
Discussion on RRM measurement operation for XR enhancements |
Hanbat National University |
| R2-2500924 |
RRM Measurement Gap/Restriction Enhancements |
Ericsson |
| R2-2501039 |
RRC-based MG skipping solution |
CMCC |
| R2-2501144 |
Discussion on RRM measurement gaps/restrictions enhancements for Rel-19 XR |
Samsung |
| R2-2501234 |
Discussion on XR RRM measurement gaps/restrictions related enhancements |
III |
| 8.7.4.1 |
LCP enhancements |
|
| R2-2500092 |
Discussion on LCP enhancements |
Qualcomm Incorporated |
| R2-2500145 |
Discussion on LCP enhancements of XR traffic |
Xiaomi Communications |
| R2-2500183 |
Consideration on LCP Enhancement |
CATT |
| R2-2500197 |
Discussion on LCP enhancements for XR |
OPPO |
| R2-2500281 |
Discussion on the adjustment of Bj/PBR for delay-aware LCP |
TCL |
| R2-2500350 |
Remaining issues on LCP enhancements for XR |
vivo |
| R2-2500378 |
Issues on Additional LCH Priority and Prioritization |
Sharp |
| R2-2500479 |
Discussions on enhancements for LCH priority-adjusted data |
Fujitsu |
| R2-2500511 |
Considerations on LCP enhancements |
NEC |
| R2-2500541 |
Discussion on LCP enhancements for XR |
DENSO CORPORATION |
| R2-2500652 |
Discussion on LCP enhancements |
HONOR |
| R2-2500679 |
Views on Delay-based Logical Channel Priority Adjustment |
Apple, Lenovo |
| R2-2500721 |
Further details on Enhanced Logical channel prioritization for XR |
Lenovo |
| R2-2500765 |
LCP Enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2500782 |
LCP enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2500792 |
LCP enhancement for XR |
InterDigital |
| R2-2500840 |
Remaining Issues on LCP Enhancements |
China Telecom |
| R2-2500853 |
Discussion on additional priority based LCP enhancements in XR |
Huawei, HiSilicon |
| R2-2500912 |
Outstanding issues on LCP enhancements for Rel-19 XR |
Samsung R&D Institute UK |
| R2-2500983 |
LCP enhancements |
Ericsson |
| R2-2501007 |
Discussion on enhanced LCP for XR |
ITRI |
| R2-2501014 |
Consideration on LCP enhancement for XR |
CMCC |
| R2-2501242 |
Discussion on LCP enhancement for XR |
LG Electronics Inc. |
| R2-2501267 |
Views on Delay-based Logical Channel Priority Adjustment |
Apple, Lenovo, Xiaomi |
| R2-2501283 |
Discussion on remaining issues related to LCP enhancements |
Rakuten Mobile, Inc |
| 8.7.4.2 |
DSR enhancements |
|
| R2-2500093 |
Discussion on DSR enhancements |
Qualcomm Incorporated |
| R2-2500146 |
Discussion on DSR enhancements of XR traffic |
Xiaomi Communications |
| R2-2500184 |
Consideration on DSR Enhancement |
CATT |
| R2-2500198 |
Discussion on DSR enhancements for XR |
OPPO |
| R2-2500293 |
Discussion on Delay status report |
CANON Research Centre France |
| R2-2500351 |
Remaining issues on DSR enhancements for XR |
vivo |
| R2-2500379 |
Issues on New DSR MAC CE |
Sharp |
| R2-2500480 |
Discussions on DSR enhancements |
Fujitsu |
| R2-2500512 |
Considerations on DSR enhancements |
NEC |
| R2-2500543 |
Discussion on DSR enhancements for XR |
DENSO CORPORATION |
| R2-2500628 |
Enhanced delay status reporting for XR |
Lenovo |
| R2-2500653 |
Discussion on DSR enhcancements |
HONOR |
| R2-2500680 |
Views on DSR Enhancements |
Apple |
| R2-2500718 |
DSR enhancements for UL scheduling |
InterDigital |
| R2-2500766 |
DSR Enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2500783 |
DSR enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2500844 |
Leftover Issues for DSR Enhancements |
China Telecom |
| R2-2500854 |
Discussion on DSR enhancements in XR |
Huawei, HiSilicon |
| R2-2500982 |
DSR enhancements |
Ericsson |
| R2-2501015 |
Consideration on DSR enhancement for XR |
CMCC |
| R2-2501136 |
DSR enhancements for UL scheduling |
ETRI |
| R2-2501139 |
Remaining issues of data reporting for enhanced DSR |
Xiaomi Communications, Apple |
| R2-2501143 |
DSR enhancements for Rel-19 XR |
Samsung |
| R2-2501153 |
MAC CE for DSR enhancement and interworking with legacy DSR |
TCL |
| R2-2501235 |
Discussion on XR DSR enhancements |
III |
| R2-2501243 |
Discussion on DSR enhancement for XR |
LG Electronics Inc. |
| R2-2501282 |
Further discussion on Rel-19 DSR enhancements |
Rakuten Mobile, Inc |
| R2-2501311 |
Discussion on DSR Enhancements for XR |
Meta |
| R2-2501348 |
Report of [AT129][504][XR] Data volume calculation for DSR |
LG Electronics |
| 8.7.5 |
RLC enhancements |
|
| R2-2500094 |
Discussion on RLC enhancements |
Qualcomm Incorporated |
| R2-2500185 |
Consideration on XR-specific RLC Enhancement |
CATT |
| R2-2500195 |
Discussion on RLC re-transmission related enhancements |
OPPO |
| R2-2500292 |
Discussion on RLC AM Enhancements |
CANON Research Centre France |
| R2-2500352 |
Discussion on RLC enhancement for XR |
vivo |
| R2-2500380 |
Discussion on RLC Enhancements |
Sharp |
| R2-2500401 |
RLC AM retransmission enhancements |
Xiaomi |
| R2-2500481 |
Discussions on RLC enhancements |
Fujitsu |
| R2-2500490 |
RLC enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2500538 |
Further details of RLC enhancements for XR |
LG Electronics Inc. |
| R2-2500544 |
Discussion on RLC enhancements |
DENSO CORPORATION |
| R2-2500629 |
AM RLC enhancement |
Lenovo |
| R2-2500654 |
Discussion on RLC enhancements |
HONOR |
| R2-2500681 |
Views on Fast RLC Retransmissions |
Apple |
| R2-2500684 |
RLC AM enhancement |
NEC |
| R2-2500698 |
RLC Enhancements for XR |
Samsung |
| R2-2500719 |
Discussion on RLC enhancements |
InterDigital |
| R2-2500747 |
RLC AM enhancements for timely retransmissions |
Sony |
| R2-2500784 |
RLC enhancements |
ZTE Corporation, Sanechips |
| R2-2500846 |
Leftover Issues for RLC AM Enhancements |
China Telecom |
| R2-2500925 |
Even More Discussions on RLC AM Enhancements |
Ericsson |
| R2-2501038 |
Discussion on the RLC AM enhancements for XR |
CMCC |
| R2-2501060 |
Discussion on RLC AM enhancements |
Huawei, HiSilicon |
| R2-2501154 |
Leftover issues for RLC AM enhancement |
TCL |
| R2-2501229 |
Discussion on RLC retransmission for XR |
Quectel |
| R2-2501251 |
Combined approach to avoid unnecessary RLC retransmissions |
Futurewei |
| R2-2501491 |
Combined approach to avoid unnecessary RLC retransmissions |
Futurewei |
| 8.7.6 |
XR rate control |
|
| R2-2500095 |
Discussion on XR rate control |
Qualcomm Incorporated |
| R2-2500186 |
Discussion on XR Rate Control |
CATT |
| R2-2500353 |
Discussion on XR rate control |
vivo |
| R2-2500381 |
Discussion on XR Rate Control |
Sharp |
| R2-2500402 |
XR rate control |
Xiaomi |
| R2-2500482 |
Discussions on XR rate control |
Fujitsu |
| R2-2500514 |
Uplink rate control for XR |
NEC |
| R2-2500539 |
Rate control signaling for XR |
LG Electronics Inc. |
| R2-2500655 |
Discussion on XR rate control |
HONOR |
| R2-2500682 |
Views on XR Rate Control |
Apple |
| R2-2500720 |
Discussion on UL congestion signaling |
InterDigital |
| R2-2500736 |
Discussion on XR rate control |
OPPO |
| R2-2500748 |
Recommended bit rate based XR rate control |
Sony |
| R2-2500785 |
XR Rate control |
ZTE Corporation, Sanechips |
| R2-2500794 |
XR Rate Control |
Lenovo |
| R2-2500807 |
Discussion on XR rate control |
Huawei, HiSilicon |
| R2-2500926 |
Even More on XR Rate Control |
Ericsson |
| R2-2501016 |
Consideration on XR rate control |
CMCC |
| R2-2501063 |
Further Discussion on Rate Control for XR |
China Telecom |
| R2-2501141 |
Discussion on UL rate control for Rel-19 XR |
Samsung |
| R2-2501202 |
XR rate control |
Nokia, Nokia Shanghai Bell |
| R2-2501312 |
Discussion on RAN Awareness and UL Rate Control for XR |
Meta |
| R2-2501347 |
LS on uplink rate control |
RAN2 |
| 8.8.1 |
Organizational |
|
| R2-2500045 |
Reply LS on requirements for ETWS primary notification (S1-244857; contact: Novamint) |
SA1 |
| R2-2500067 |
Reply LS on Supporting MBS broadcast service for NR NTN (S2-2501329; contact: Xiaomi) |
SA2 |
| R2-2500529 |
Introduction of LTE TN to NR NTN IDLE mode mobility |
CATT |
| R2-2500705 |
Introduction of LTE TN to NR NTN Mobility UE Capability |
vivo |
| R2-2501284 |
Introduction of stage 2 for LTE TN to NR NTN idle mode mobility |
Samsung |
| R2-2501304 |
Running RRC CR for NR NTN phase 3 |
Ericsson |
| R2-2501321 |
Introduction of NTN Ph3 enhancements |
THALES (Rapporteur) |
| R2-2501416 |
Introduction of stage 2 for LTE TN to NR NTN idle mode mobility |
Samsung |
| R2-2501417 |
Introduction of LTE TN to NR NTN Mobility UE Capability |
vivo |
| R2-2501418 |
Introduction of LTE TN to NR NTN IDLE mode mobility |
CATT |
| 8.8.2 |
Downlink coverage enhancements |
|
| R2-2500100 |
Discussion on DL coverage enhancement |
Xiaomi |
| R2-2500148 |
Discussion on downlink coverage enhancement |
LG Electronics Inc. |
| R2-2500219 |
Discussion on Downlink Coverage Enhancement |
Samsung |
| R2-2500459 |
Discussion on DL coverage enhancement for NTN |
OPPO |
| R2-2500483 |
Discussions on downlink coverage enhancement |
Fujitsu |
| R2-2500524 |
Further discussion on downlink coverage enhancements |
CATT |
| R2-2500532 |
Default extended SSB periodicity |
Qualcomm Incorporated |
| R2-2500575 |
Further discussion of NR NTN coverage enhancement |
China Telecom |
| R2-2500582 |
DL coverage enhancement in NTN |
Apple |
| R2-2500615 |
Cell barring and reselection for NTN DL-CE |
Lenovo |
| R2-2500656 |
Discussion on downlink coverage enhancement |
HONOR |
| R2-2500685 |
Downlink coverage enhancement |
NEC |
| R2-2500689 |
Discussion on DL coverage enhancements |
Huawei, HiSilicon, Turkcell |
| R2-2500727 |
Discussion on NTN downlink coverage enhancement |
Nokia |
| R2-2500749 |
SMTC impacts due to NTN downlink coverage enhancements |
Sony |
| R2-2501010 |
Discussion on SMTC for NTN DL coverage enhancements |
ITRI |
| R2-2501037 |
Analysis on DL coverage enhancements due to extended SIB periodicity |
CMCC |
| R2-2501160 |
Discussion on Downlink Coverage Enhancements |
CSCN |
| R2-2501179 |
Downlink coverage enhancement for non-terrestrial networks |
InterDigital Communications |
| R2-2501182 |
Discussion on Downlink Coverage Enhancements |
Sharp |
| R2-2501280 |
Discussion on NR NTN Downlink Coverage Enhancements |
Rakuten Mobile, Inc |
| R2-2501290 |
Downlink coverage enhancement SMTC impacts |
Sequans Communications |
| R2-2501291 |
Downlink coverage enhancement access control |
Sequans Communications |
| R2-2501318 |
DL coverage enhancements |
Ericsson |
| R2-2501415 |
Report of [AT129][304][R19 NR NTN] LS to RAN1 on DL coverage enhancements (Huawei) |
Huawei, HiSilicon |
| 8.8.3 |
Uplink Capacity/Throughput Enhancement |
|
| R2-2500665 |
UL Capacity enhancement for NRNTN |
NEC Corporation |
| R2-2500690 |
Discussion on Uplink Capacity Enhancements |
Huawei, HiSilicon, Turkcell |
| R2-2500770 |
Consideration on DL CE and UL capacity enhancement |
ZTE Corporation, Sanechips |
| R2-2501032 |
Discussion on uplink capacity/throughput enhancement for NR NTN |
CMCC |
| R2-2501281 |
RAN2 related proposals for Uplink Capacity & Throughput Enhancements |
Rakuten Mobile, Inc |
| 8.8.4 |
Support of Broadcast service |
|
| R2-2500079 |
Further Discussion on MBS Broadcast Service Area Provision in NTN |
vivo |
| R2-2500080 |
Discussion on MBS Broadcast Service Continuity in NTN |
vivo |
| R2-2500220 |
Discussion on Broadcast Service Area |
Samsung |
| R2-2500252 |
Discussion on Support of MBS Broadcast Service |
TCL |
| R2-2500331 |
Further Details on MBS in Rel-19 NR NTN |
Nokia, Nokia Shanghai Bell |
| R2-2500453 |
Discussion on providing MBS service area in NTN network |
OPPO |
| R2-2500465 |
Discussion on the support of broadcast service |
Xiaomi |
| R2-2500484 |
Discussions on supporting broadcast service |
Fujitsu |
| R2-2500523 |
Further discussion on support of broadcast service in NR NTN |
CATT |
| R2-2500530 |
Signaling of MBS broadcast service area information |
Qualcomm Incorporated |
| R2-2500576 |
The mapping between service area information and MBS session |
China Telecom |
| R2-2500583 |
Discussion on broadcast serivce over NTN |
Apple |
| R2-2500616 |
Further considerations on broadcast service area information in NTN |
Lenovo |
| R2-2500657 |
Discussion on the support of broadcast service |
HONOR |
| R2-2500675 |
Remaining issues on the support of broadcast service in NTN |
ETRI |
| R2-2500771 |
Consideration on broadcast service support |
ZTE Corporation, Sanechips |
| R2-2500966 |
Discussion on MBS broadcast over NTN |
Huawei, HiSilicon, Turkcell |
| R2-2501005 |
Discussion on MII procedure in NTN |
LG Electronics France |
| R2-2501033 |
Considerations on broadcast service for NR NTN |
CMCC |
| R2-2501180 |
Support for broadcast service in non-terrestrial networks |
InterDigital Communications |
| R2-2501181 |
Remaining issues on intended service area |
Sharp |
| R2-2501306 |
Support for broadcast services in NR NTN |
Ericsson |
| R2-2501522 |
Draft LS on Inclusion of NTN intended service area in the Service Announcement |
Ericsson |
| R2-2501528 |
Draft LS on warning area coordinates |
Ericsson |
| R2-2501581 |
Geofencing in ETWS for NR and NB-IoT NTN |
RAN2 |
| R2-2501583 |
Inclusion of NTN intended service area in the Service Announcement |
RAN2 |
| 8.8.5 |
Support of regenerative payload |
|
| R2-2500617 |
UE location verification in NTN regenerative architecture |
Lenovo |
| R2-2500750 |
Satellite switch with re-sync in regenerative payload |
Sony |
| R2-2500904 |
Regenerative payload for NTN for NR Ph3 |
TOYOTA Info Technology Center |
| R2-2501066 |
Discussion on regenerative payload |
Fujitsu Limited |
| R2-2501097 |
Discussion on the impact of regenerative payload |
ETRI |
| 8.8.6 |
LTE to NR NTN mobility |
|
| R2-2500081 |
Discussion on Redirection from E-UTRA TN to NR-NTN |
vivo |
| R2-2500330 |
On E-UTRAN TN to NR NTN enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2500460 |
Discussion on dedicated priority and redirection via RRCConnectionRelease |
OPPO |
| R2-2500466 |
Discussion on the redirection from LTE to NR NTN |
Xiaomi |
| R2-2500526 |
Discussion on redirection from LTE TN to NR NTN |
CATT |
| R2-2500531 |
Frequency priorities and redirection from LTE to NR NTN |
Qualcomm Incorporated |
| R2-2500577 |
Signalling design for NTN mobility redirection |
China Telecom |
| R2-2500687 |
Redirection from E-UTRN TN to NR NTN |
NEC |
| R2-2500772 |
Consideration on LTE TN to NR NTN mobility |
ZTE Corporation, Sanechips |
| R2-2501272 |
Re-direction from E-UTRAN TN to NR NTN |
Samsung |
| R2-2501305 |
E-UTRAN TN to NR-NTN mobility |
Ericsson |
| 8.9.1 |
Organizational |
|
| R2-2500010 |
Reply LS on OCC for CB-msg3 NPUSCH (R1-2410895; contact: Sony) |
RAN1 |
| R2-2500044 |
Reply LS on PWS support for NB-IoT NTN (S1-244757; contact: Novamint) |
SA1 |
| R2-2500061 |
Reply to Reply LS on FS_5GSAT_Ph3_ARCH conclusions (S2-2501085; contact: China Telecom) |
SA2 |
| R2-2500204 |
RRC Running CR for IoT NTN |
Huawei, HiSilicon |
| R2-2501158 |
MAC Running CR for Rel-19 IoT NTN |
MediaTek Inc. |
| R2-2501320 |
Draft Introduction of IoT NTN phase 3 |
Ericsson |
| R2-2501523 |
RRC Running CR for IoT NTN |
Huawei, HiSilicon |
| R2-2501524 |
MAC Running CR for Rel-19 IoT NTN |
MediaTek Inc. |
| R2-2501525 |
Draft Introduction of IoT NTN phase 3 |
Ericsson |
| 8.9.2 |
Support of Store & Forward |
|
| R2-2500071 |
Discussion on Store and Forward operation |
Xiaomi |
| R2-2500082 |
Further Discussion on S&F Operation |
vivo |
| R2-2500106 |
S&F enhancements |
PANASONIC |
| R2-2500309 |
Discussion on Store & Forward satellite operation |
OPPO |
| R2-2500366 |
Further consideration on S&F operation in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2500418 |
Discussion on time information for S&F |
ASUSTeK |
| R2-2500467 |
Open issues on the S&F operation |
Google |
| R2-2500525 |
Discussion on RAN2 impacts for the support of S&F operation |
CATT |
| R2-2500533 |
Switching of S&F mode |
Qualcomm Incorporated |
| R2-2500578 |
Time information of IoT NTN Store & Forward |
China Telecom |
| R2-2500586 |
Support of S&F operation in IoT NTN |
Apple |
| R2-2500618 |
Enhancements to support S&F operation |
Lenovo |
| R2-2500658 |
Discussion on the Store and Forward satellite operation |
HONOR |
| R2-2500686 |
Radio Interface Aspect of S&F |
NEC |
| R2-2500704 |
Further consideration on Store and Forward |
Huawei, HiSilicon |
| R2-2500762 |
Discussion on support of Store&Forward |
Transsion Holdings |
| R2-2500796 |
RAN2 impacts for SF Operation |
Nokia , Nokia Shanghai Bells |
| R2-2500876 |
Support of Store and Forward. |
Interdigital, Inc. |
| R2-2500922 |
Discussion on Paging and Mode Switching |
TOYOTA Info Technology Center |
| R2-2500929 |
Support of Store & Forward for IoT NTN |
TURKCELL |
| R2-2500980 |
Further considerations on S&F operations |
Continental Automotive |
| R2-2501004 |
Discussion on Store & Forward operation |
DENSO CORPORATION |
| R2-2501012 |
Discussion on IoT NTN Store and Forward |
CMCC |
| R2-2501159 |
RAN2 impact on S&F mode |
MediaTek Inc. |
| R2-2501273 |
Discussion on Store and Forward operation |
Samsung |
| R2-2501307 |
Support for store and forward in IoT NTN |
Ericsson |
| 8.9.3 |
Uplink Capacity Enhancement |
|
| R2-2500072 |
Discussion on uplink capacity enhancements for IoT NTN |
Xiaomi |
| R2-2500083 |
Discussion on CB-Msg3 Mechanism |
vivo |
| R2-2500096 |
Further discussion on CB-Msg3 Mechanism |
NTU |
| R2-2500138 |
Further considerations on Locating of Replicas for DSA |
NTPU |
| R2-2500162 |
Remaining issues on CB-Msg3 transmission |
Spreadtrum, UNISOC |
| R2-2500200 |
Further consideration on UL capacity enhancement |
Huawei, HiSilicon, Turkcell |
| R2-2500310 |
Discussion on CB-msg3 EDT and msg4 enhancement |
OPPO |
| R2-2500367 |
Further consideration on UL capacity enhancements in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2500528 |
Further consideration on UL capacity enhancements |
CATT |
| R2-2500534 |
CB-Msg3 and Msg4 enhancements |
Qualcomm Incorporated |
| R2-2500548 |
Further discussion on UL capacity enhancement for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2500579 |
Consideration of CB Msg3-EDT in IoT NTN |
China Telecom |
| R2-2500585 |
Uplink capacity enhancement in IoT NTN |
Apple |
| R2-2500619 |
EDT for uplink capacity enhancement in NTN |
Lenovo |
| R2-2500659 |
Discussion on UL capacity enhancement |
HONOR |
| R2-2500664 |
Discussion on UL Capacity Enhancement for IoT-NTN |
NEC Corporation |
| R2-2500763 |
Discussion on uplink capacity enhancement |
Transsion Holdings |
| R2-2500848 |
IoT-NTN uplink capacity enhancement |
Nordic Semiconductor ASA |
| R2-2500877 |
EDT/PUR enhancements. |
Interdigital, Inc. |
| R2-2500981 |
Discussion on EDT Enhancements for IOT NTN |
Skylo Technologies |
| R2-2501034 |
Considerations on uplink capacity enhancement for IoT-NTN |
CMCC |
| R2-2501164 |
Discussion on CB-Msg3 procedure |
MediaTek Inc. |
| R2-2501265 |
Implicit pointer for locating CB-Msg3 DSA replicas |
DLR, ESA, Toyota ITC, Inmarsat, Viasat, Thales, Aalyria Technologies, Echostar, Eutelsat Group Sateliot, Novamint |
| R2-2501274 |
Further issues on contention-based Msg3 |
Samsung |
| R2-2501319 |
UL capacity enhancements for IoT NTN |
Ericsson |
| R2-2501419 |
Report of [AT129][305][R19 IoT NTN] CB-msg3 parameters |
Ericsson |
| R2-2501420 |
Report of [AT129][306][R19 IoT NTN] TX and RX window for CB-msg3 |
MediaTek |
| 8.9.4 |
Support of PWS |
|
| R2-2500073 |
PWS support for NB-IoT over NTN |
Xiaomi |
| R2-2500084 |
Further Discussion on PWS Support for NB-IoT |
vivo |
| R2-2500311 |
Discussion on PWS for NB-IoT |
OPPO |
| R2-2500342 |
Remaining issues on PWS support for NB-IoT |
Huawei, HiSilicon, Turkcell |
| R2-2500368 |
Further consideration on PWS support in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2500464 |
Discussion on the support for PWS in NB-IoT |
Google |
| R2-2500522 |
Remaining issues on support of PWS for NB-IoT NTN UE |
CATT |
| R2-2500535 |
Discussion on PWS in NB-IoT NTN |
Qualcomm Incorporated |
| R2-2500580 |
Remaining issues for PWS in IoT NTN |
China Telecom |
| R2-2500620 |
PWS broadcast support for NB-IoT in NTN |
Lenovo |
| R2-2500641 |
Considering on PWS Support in NB-IoT |
NEC Corporation |
| R2-2500797 |
On PWS support for NB-IoT NTN |
Nokia , Nokia Shanghai Bells |
| R2-2500952 |
Discussion on remaining issues for support of PWS message |
KT Corp. |
| R2-2501035 |
Support of PWS messages for NB-IoT |
CMCC |
| R2-2501161 |
Discussion on supporting PWS for NB-IoT |
MediaTek Inc. |
| R2-2501275 |
Impact of introducing PWS broadcasting for NB-IoT |
Samsung |
| R2-2501308 |
Enhancements to support PWS in NB-IoT NTN |
Ericsson |
| R2-2501322 |
On PWS support for NB-IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2501529 |
Draft LS on maximum warning message size |
Google |
| R2-2501570 |
LS to CT1 and CT4 on maximum warning message size |
RAN2 |
| R2-2501586 |
LS to CT1 and CT4 on maximum warning message size |
RAN2 |
| 8.10.1 |
Organizational |
|
| R2-2500025 |
Reply LS on MHI enhancement solution for SCG deactivation/activation (R3-247906; contact: Huawei) |
RAN3 |
| R2-2500026 |
LS on RAN3 agreements with impact on UE related to the Rel-19 SON/MDT (R3-247908; contact: Samsung) |
RAN3 |
| R2-2500918 |
Running CR for SONMDT features |
Ericsson |
| 8.10.2.1 |
LTM |
|
| R2-2500234 |
MRO Enhancements for LTM |
CATT |
| R2-2500363 |
MRO for LTM |
Nokia |
| R2-2500419 |
Discussion on random access report for LTM |
ASUSTeK |
| R2-2500558 |
Outstanding issues of MRO |
Apple |
| R2-2500622 |
Discussion on MRO enhancements for LTM |
Lenovo |
| R2-2500706 |
Discussion on MRO enhancement for LTM |
China Unicom |
| R2-2500831 |
MRO for LTM |
ZTE Corporation, Sanechips |
| R2-2500859 |
MRO enhancements for LTM |
Samsung |
| R2-2500916 |
Further considerations on MRO for LTM |
Ericsson |
| R2-2501044 |
MRO enhancements for LTM |
CMCC |
| R2-2501104 |
Discussion on MRO for LTM |
Huawei, HiSilicon |
| R2-2501212 |
MRO for LTM |
LG Electronics Inc. |
| R2-2501255 |
SON and MDT for LTM |
Qualcomm Incorporated |
| R2-2501378 |
LS on SON for LTM |
RAN2 |
| 8.10.2.2 |
CHO with candidate SCGs |
|
| R2-2500235 |
MRO Enhancements for CHO with Candidate SCGs |
CATT |
| R2-2500364 |
MRO for CHO with candidate SCG |
Nokia |
| R2-2500623 |
Discussion on MRO enhancements for CHO with candidate SCGs |
Lenovo |
| R2-2500674 |
MRO for CHO with candidate SCG(s) |
NEC |
| R2-2500707 |
Discussion on MRO enhancement for CHO with candidate SCGs |
China Unicom |
| R2-2500832 |
MRO for CHO with candidate SCGs |
ZTE Corporation, Sanechips |
| R2-2500855 |
MRO enhancements for CHO with Candidate SCG(s) |
Samsung |
| R2-2501084 |
Discussion on new triggering condition of SHR for CHO with candidate SCGs |
vivo |
| R2-2501105 |
Discussion on MRO for CHO with candidate SCGs |
Huawei, HiSilicon |
| R2-2501200 |
SON enhancement for CHO with candidate SCG |
SHARP Corporation |
| R2-2501213 |
MRO for CHO and Associated CPAC |
LG Electronics Inc. |
| R2-2501256 |
SON and MDT for CHO with candidate SCGs |
Qualcomm Incorporated |
| R2-2501285 |
SON support for CHO with Candidate SCG |
Ericsson |
| 8.10.4 |
SON/MDT for NTN |
|
| R2-2500236 |
Consideration on SONMDT enhancements for intra-NTN mobility |
CATT |
| R2-2500571 |
Discussion on SON of intra-NTN mobility |
China Telecom |
| R2-2500624 |
Discussion on MRO for intra-NTN mobility |
Lenovo |
| R2-2500708 |
Discussion on SONMDT for NTN mobility |
China Unicom |
| R2-2500833 |
MRO and MDT for NTN |
ZTE Corporation, Sanechips |
| R2-2500861 |
SON/MDT for NTN |
Samsung |
| R2-2500917 |
Discussion on the reply LS to RAN3 on SON-MDT enhancements for NTN |
Ericsson |
| R2-2500978 |
Area Scope for the logged MDT for NTN |
Nokia |
| R2-2501046 |
SON/MDT enhancements for NTN |
CMCC |
| R2-2501106 |
Discussion on SONMDT for NTN |
Huawei, HiSilicon |
| R2-2501214 |
NTN Logging for Unchanged PCI Mobility |
LG Electronics Inc. |
| R2-2501257 |
SON and MDT for NTN |
Qualcomm Incorporated |
| 8.10.5.1 |
SDT |
|
| R2-2500625 |
Discussion on RACH optimization for SDT |
Lenovo |
| R2-2500834 |
Rel-18 leftovers and LS from RAN3 |
ZTE Corporation, Sanechips |
| R2-2501085 |
RA report optimization for SDT |
vivo |
| R2-2501107 |
Discussion on leftovers from Rel-18 |
Huawei, HiSilicon |
| R2-2501199 |
RA report optimization for SDT |
SHARP Corporation |
| R2-2501258 |
SON and MDT for SDT |
Qualcomm Incorporated |
| R2-2501289 |
On Rel.18 leftovers |
Ericsson |
| 8.10.5.3 |
Other |
|
| R2-2500237 |
MHI Enhancement for SCG Activation and Deactivation |
CATT |
| R2-2500365 |
MHI/UHI Enhancement for SCG Deactivation/Activation |
Nokia |
| R2-2500867 |
MHI Enhancement for SCG Deactivation/Activation |
Samsung |
| R2-2501045 |
MHI and UHI Enhancement for SCG Deactivation Activation |
CMCC, CATT, Ericsson, Huawei, Lenovo, ZTE |
| R2-2501047 |
[Draft] Reply LS on MHI enhancement solution for SCG deactivation/activation |
CMCC |
| R2-2501108 |
Draft Reply LS on MHI enhancement solution for SCG deactivation/activation |
Huawei, HiSilicon |
| 8.11.1 |
Organizational |
|
| R2-2500036 |
LS on CSI-RS measurement with SBFD operation (R4-2420165; contact: MediaTek) |
RAN4 |
| R2-2500273 |
38300 Running CR for SBFD |
CATT |
| R2-2500886 |
SBFD UE capabilities running CR |
Ericsson |
| 8.11.2 |
Random access in SBFD |
|
| R2-2500098 |
Impacts on the random access by the evolution of duplex operation |
Huawei, HiSilicon |
| R2-2500105 |
Random Access Operation of SBFD |
Nokia Corporation |
| R2-2500109 |
SBFD Configuration for initial random access and operations |
Charter Communications, Inc |
| R2-2500191 |
Discussion on RACH in SBFD |
Xiaomi |
| R2-2500274 |
Discussion on Random Access in SBFD symbols |
CATT |
| R2-2500298 |
Random Access for SBFD Operation |
NEC |
| R2-2500337 |
Discussion on random access procedure in SBFD |
vivo |
| R2-2500339 |
Discussion on Random Access operation in SBFD |
InterDigital, Inc. |
| R2-2500376 |
Random Access Issues for SBFD |
Sharp |
| R2-2500588 |
Remaining issues for RACH in SBFD |
Apple |
| R2-2500606 |
Discussion on random access procedure in SBFD |
ZTE Corporation |
| R2-2500751 |
Random access for SBFD Operation |
Sony |
| R2-2500884 |
SBFD RA aspects |
Ericsson |
| R2-2501029 |
Discussion on random access in SBFD |
CMCC |
| R2-2501129 |
Views on random access for SBFD |
Qualcomm Incorporated |
| R2-2501135 |
Random access in SBFD |
Samsung |
| R2-2501244 |
Discussion on Random Access in SBFD |
LG Electronics Inc. |
| 8.11.3 |
Other aspects |
|
| R2-2500110 |
Cross link interference handling in SBFD networks |
Charter Communications, Inc |
| R2-2500275 |
Discussion on other aspects of SBFD |
CATT |
| R2-2500338 |
SBFD other aspects |
vivo |
| R2-2500340 |
Discussion on resource configuration in SBFD |
InterDigital, Inc. |
| R2-2500403 |
Other aspects of SBFD |
Xiaomi |
| R2-2500554 |
Other aspects of SBFD |
Nokia |
| R2-2500607 |
Discussion on L3 and L1 measurement in SBFD |
ZTE Corporation |
| R2-2500637 |
Other impacts by the evolution of duplex operation |
Huawei, HiSilicon |
| R2-2500885 |
CSI-RS measurements for RLM/BFD/CBD in SBFD |
Ericsson |
| R2-2501130 |
Other aspects of SBFD |
Qualcomm Incorporated |
| R2-2501170 |
Other Aspects of SBFD |
Samsung |
| 8.12.1 |
Organizational |
|
| R2-2500008 |
LS to RAN2 on RRC and MAC impacts for Rel-19 NR MIMO Ph5 (R1-2410758; contact: Samsung) |
RAN1 |
| R2-2501026 |
Work Plan for Rel-19 on NR MIMO Phase 5 |
CMCC,Samsung,MediaTek |
| 8.12.2 |
Asymmetric DL sTRP/UL mTRP |
|
| R2-2500104 |
RAN2 Aspects of Asymmetric DL sTRP/UL mTRP |
Nokia Corporation |
| R2-2500179 |
Discussion on asymmetric DL sTRP/UL mTRP |
China Telecom |
| R2-2500217 |
Discussion on Asymmetric DL sTRP/UL mTRP |
Samsung |
| R2-2500249 |
Discussion on Asymmetric DL sTRP UL mTRP |
CATT |
| R2-2500268 |
Discussion on asymmetric DL sTRP and UL mTRP |
Xiaomi |
| R2-2500354 |
Discussion on MAC CE impact for asymmetric DL sTRP/UL mTRP scenarios |
vivo |
| R2-2500450 |
Discussion on asymmetric DL sTRP and UL mTRP |
SHARP Corporation |
| R2-2500635 |
Discussion on PL offset |
Lenovo |
| R2-2500752 |
Enhancement for Asymmetric DL sTRP/UL mTRP |
Sony |
| R2-2500825 |
Consideration on Asymmetric DL sTRP/UL mTRP |
LG Electronics Inc. |
| R2-2500975 |
Asymmetric DL/UL mTRP user plane impact from MIMO ph. 5 |
Ericsson |
| R2-2501024 |
Discussion on Asymmetric DL sTRP/UL mTRP |
CMCC |
| R2-2501166 |
Discussion on UL only mTRP |
Qualcomm Incorporated |
| R2-2501177 |
Discussion on Asymmetric DL sTRP/UL mTRP |
Huawei, HiSilicon |
| R2-2501222 |
Consideration on the Asymmetric DL sTRP/UL mTRP |
ZTE Corporation |
| 8.12.3 |
Others |
|
| R2-2500103 |
RAN2 Aspects of the NR MIMO |
Nokia Corporation |
| R2-2500180 |
Discussion on UE initiated beam reporting |
China Telecom |
| R2-2500210 |
Discussion on UEI beam reporting |
OPPO |
| R2-2500218 |
Discussion on UE-initiated Beam Reporting and CSI enhancement |
Samsung |
| R2-2500250 |
Discussion on UE-initiated Beam Reporting and CSI Enhancement |
CATT |
| R2-2500269 |
Discussion on modelling of UE-initiated beam report |
Xiaomi |
| R2-2500355 |
Discussion on UE-initiated/event-driven beam management |
vivo |
| R2-2500451 |
Discussion on UE-initiated/event-driven beam management |
SHARP Corporation |
| R2-2500636 |
Discussion on UEIBR |
Lenovo |
| R2-2500826 |
Discussion on UEI beam reporting impact |
LG Electronics Inc. |
| R2-2500930 |
Impacts from other NR MIMO Phase 5 objectives |
Ericsson |
| R2-2501025 |
Discussion on UE-initiated/event-driven beam management |
CMCC |
| R2-2501167 |
Discussion on UE Initiated Beam Report |
Qualcomm Incorporated |
| R2-2501176 |
Enhancements for UE-initiated/event-driven beam management |
Huawei, HiSilicon |
| R2-2501223 |
Consideration on the UEIBM |
ZTE Corporation |
| 8.13.1 |
Organizational |
|
| R2-2500064 |
LS on Authorization information for Layer-2 multi-hop U2N relaying to NG-RAN (S2-2501296; contact: LGE) |
SA2 |
| R2-2500068 |
Reply LS on relay discovery announcement (S2-2501334; contact: LGE) |
SA2 |
| R2-2500866 |
Introduction of multi-hop U2N relay in TS 38.323 |
Ericsson |
| 8.13.2 |
Relay discovery and (re)selection |
|
| R2-2500122 |
Discussion on multi-hop U2N relay discovery and relay selection |
NEC |
| R2-2500187 |
Discussion on Multi-hop Discovery and (Re)selection |
CATT |
| R2-2500192 |
Discovery and relay (re)selection for multi-hop U2N relay |
OPPO |
| R2-2500307 |
Considerations on relay discovery and (re)selection |
Samsung |
| R2-2500420 |
One remaining issue on multi-hop U2N Relay Discovery message forwarding |
ASUSTeK |
| R2-2500432 |
Relay discovery and selection for Multi-hop UE-to-NW Relay |
Apple |
| R2-2500497 |
Discovery and Relay (Re)Selection for Multi-hop U2N Relays |
InterDigital |
| R2-2500508 |
Discussion on the discovery and relay (re)selection for multi-hop U2N relay |
LG Electronics Inc. |
| R2-2500570 |
Consideration on multi-hop relay discovery and reselection |
China Telecom |
| R2-2500632 |
Relay (re)selection in Multi-hop relay |
Lenovo |
| R2-2500700 |
Relay discovery and (re)selection for multi-hop Relay |
Huawei, HiSilicon |
| R2-2500723 |
[Draft] LS on legacy UE participation in multi-hop UE communication |
Nokia |
| R2-2500724 |
Relay discovery and (re)selection |
Nokia |
| R2-2500753 |
Multi-hop relay selection/re-selection |
Sony |
| R2-2500865 |
Discussion on relay discovery and relay (re)selection |
Ericsson |
| R2-2500905 |
Discussion on multi-hop Relay discovery and (re)selection |
ZTE Corporation, Sanechips |
| R2-2500933 |
Discovery and (re)selection under multihop relay |
Kyocera |
| R2-2501118 |
Discussion on topology and intermediate relay UE (re)selection |
vivo |
| R2-2501174 |
Relay discovery and (re)selection |
TCL |
| R2-2501183 |
discussion on Relay discovery and (re)selection for multi-hop relay |
Sharp |
| R2-2501259 |
Discovery and Relay (re)selection for multi-hop U2N relay |
Qualcomm Incorporated |
| R2-2501433 |
[AT129][410][Relay]Intermediate Relay UE (re)selection (vivo) |
vivo |
| 8.13.3 |
Control Plane Procedures and SRAP impact |
|
| R2-2500188 |
Discussion on the Control Plane Procedures |
CATT |
| R2-2500194 |
Control plane procedures of multi-hop U2N relay |
OPPO |
| R2-2500300 |
Control Plane aspects for Multi-hop Relay |
NEC |
| R2-2500308 |
Consideration on CP issues for multi-hop SL relay |
Samsung |
| R2-2500433 |
Discussion on Control Plane for Multi-hop UE-to-NW Relay |
Apple |
| R2-2500434 |
Discussion on SRAP for Multi-hop Layer-2 U2N Relay |
Apple |
| R2-2500496 |
Report of [Post128][401][Relay] Control Plane Baseline Solution |
InterDigital |
| R2-2500498 |
Control Plane Handling for Multi-hop U2N Relays |
InterDigital |
| R2-2500509 |
Discussion on the control plane procedure for multi-hop U2N relay |
LG Electronics Inc. |
| R2-2500561 |
Discussion on control plane aspects for NR sidelink multi-hop relay |
China Telecom |
| R2-2500633 |
Control plane in Multi-hop relay |
Lenovo |
| R2-2500701 |
Control plane procedures for multi-hop relay |
Huawei, HiSilicon |
| R2-2500725 |
SRAP impacts on MH relay |
Nokia |
| R2-2500864 |
Discussion on control plane procedures |
Ericsson, Apple, AT&T, InterDigital Inc, FirstNet, Qualcomm Incorporated |
| R2-2500898 |
Discussion on control plane procedures for multi-hop SL Relay |
ZTE Corporation, Sanechips |
| R2-2500913 |
SRAP design for R19 multi-hop SL relaying |
Samsung R&D Institute UK |
| R2-2500934 |
Control Plane under multihop L2 U2N relaying |
Kyocera |
| R2-2500953 |
Discussion on control plane procedure for SL multi-hop relay |
KT Corp. |
| R2-2501119 |
Discussion on CP and SRAP impact for baseline procedure |
vivo |
| R2-2501184 |
discussion on C-plane procedure for multi-hop relay |
Sharp |
| R2-2501260 |
Open issue for control plane approach 1 |
Qualcomm Incorporated |
| R2-2501421 |
[AT129][401][Relay] SRAP for Rel-19 multihop relay (OPPO) |
OPPO |
| 8.13.4 |
Service continuity |
|
| R2-2500189 |
Intra-gNB Service Continuity for Multi-hop U2N Relay |
CATT |
| R2-2500193 |
Service continuity of multi-hop U2N relay |
OPPO |
| R2-2500421 |
RRC states of candidate Relay UEs for path switching |
ASUSTeK |
| R2-2500510 |
Discussion on service continuity for multi-hop U2N relay |
LG Electronics Inc. |
| R2-2500562 |
Discussion on service continuity for multi-hop relay |
China Telecom |
| R2-2500634 |
Service continuity for Multi-hop system |
Lenovo |
| R2-2500702 |
Discussion on service continuity for Multi-hop Relay |
Huawei, HiSilicon |
| R2-2500733 |
Considerations on Service Continuity of Multi-hop Relay |
NEC |
| R2-2500906 |
Discussion on service continuity for multi-hop SL relay |
ZTE Corporation, Sanechips |
| R2-2500927 |
Intra-gNB Service Continuity for Multi-Hop Relays |
Ericsson |
| R2-2500935 |
Service Continuity for U2N multihop relay |
Kyocera |
| R2-2501120 |
Discussion on Service continuity for multi-hop relay |
vivo |
| R2-2501185 |
discussion on service continuity for multi-hop relay |
Sharp |
| 8.14 |
Additional topological enhancements |
|
| R2-2500016 |
Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell (R3-244830; contact: Ericsson) |
RAN3 |
| R2-2500027 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) (R3-247909; contact: Samsung) |
RAN3 |
| R2-2500028 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) (R3-247910; contact: Qualcomm) |
RAN3 |
| R2-2500046 |
Reply LS on Clarification regarding definition of 5G NR femto ownership (S2-2411241; contact: LGE) |
SA2 |
| R2-2500065 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) (S2-2501324; contact: Ericsson) |
SA2 |
| R2-2500069 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) (S2-2501336; contact: Nokia) |
SA2 |
| 8.15 |
NavIC L1 SPS A-GNSS support |
|
| R2-2500108 |
Introduction of NavIC L1 SPS A-GNSS in LPP |
Reliance Jio, ISRO, Ericsson, MediaTek, CEWiT |
| R2-2500361 |
[Post128][403][POS] NavIC L1 stage 3 CR check (Reliance Jio) |
Reliance Jio |
| R2-2500811 |
Discussion on the support of NavIC L1 SPS |
Huawei, HiSilicon |
| R2-2500972 |
NavIC broadcast ephemeris to refer to for GNSS SSR corrections |
Ericsson, Reliance Jio |
| 8.16 |
BDS B2b in A-GNSS |
|
| R2-2500278 |
[Post128][402][POS] BDS B2b stage 3 CR check (CATT) |
CATT |
| R2-2500279 |
Introduction of B2b signal in BDS system in A-GNSS |
CATT, CAICT, Ericsson, Huawei, HiSilicon |
| R2-2500810 |
Discussion on the remaining issues for BDS B2b |
Huawei, HiSilicon |
| R2-2500973 |
Remaining issues of BDS B2b Signal Addition |
Ericsson |
| R2-2501435 |
Introduction of B2b signal in BDS system in A-GNSS |
CATT, CAICT, Ericsson, Huawei, HiSilicon |
| 8.17 |
IoT-NTN TDD mode |
|
| R2-2500085 |
Discussion on RAN2 Imapcts of IoT-NTN TDD Mode |
vivo |
| R2-2500175 |
Work plan for WID: introduction of IoT-NTN TDD mode |
Iridium Satellite LLC |
| R2-2500206 |
Discussion on RAN2 impacts of IoT-NTN TDD |
Huawei, HiSilicon |
| R2-2500312 |
Discussion on IoT NTN TDD mode |
OPPO |
| R2-2500390 |
Discussion on IoT-NTN TDD mode |
Iridium Satellite LLC |
| R2-2500527 |
Discussion on support of IoT NTN TDD |
CATT |
| R2-2500536 |
Discussion on new NB-IoT NTN TDD mode |
Qualcomm Incorporated |
| R2-2500549 |
Discussion on support of TDD mode for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2500587 |
Discussion on supporting IoT NTN TDD mode |
Apple |
| R2-2500621 |
Discussion on TDD support in IoT NTN |
Lenovo |
| R2-2500773 |
Consideration on IoT-NTN TDD mode |
ZTE Corporation, Sanechips |
| R2-2500923 |
Signaling aspects of IoT-NTN TDD mode |
TOYOTA Info Technology Center |
| R2-2500936 |
Discussion of adaptions to support IoT-NTN TDD |
THALES |
| R2-2501036 |
Support of IoT-NTN TDD mode |
CMCC |
| R2-2501277 |
Initial aspects on IoT NTN TDD |
Samsung |
| R2-2501521 |
Draft LS on H-SFN aspects for IoT NTN TDD mode |
Samsung |
| 8.18 |
TEI19 |
|
| R2-2500031 |
Reply LS on RAN3 vs RAN2 Basketball Match (R3-247925; contact: ZTE) |
RAN3 |
| R2-2500086 |
On LTE TN to NB-IoT NTN Mobility Handling |
vivo |
| R2-2500111 |
Discussion on ProSe for NPN |
OPPO |
| R2-2500362 |
ProSe support in NPN [ProSe_NPN] |
Nokia, ZTECorporation, Sanechips, LGE, Philips |
| R2-2500370 |
Handling downlink BWP restriction for MT-SDT |
Samsung |
| R2-2500422 |
ProSe support in NPN [ProSe_NPN] |
ZTE Corporation, Sanechips, Nokia, LGE, Philips |
| R2-2500662 |
SDT enhancement for DL bandwidth restriction |
NEC Corporation |
| R2-2500754 |
Initial DL BWP restriction for MT-SDT |
Sony |
| R2-2500776 |
Addressing Bandwidth Restrictions for MT-SDT |
Ericsson, T-Mobile US, Deutsche Telekom |
| R2-2500780 |
SDT on separate BWP |
ZTE Corporation, Sanechips |
| R2-2500820 |
Discussion on the control parameters for on-demand posSIB request [PosOdSIB-Req] |
Huawei, HiSilicon, CATT, Ericsson, Qualcomm |
| R2-2500823 |
BWP restriction in MT-SDT |
LG Electronics Inc. |
| R2-2500897 |
Discussion on SDT data transmission restrictions |
Huawei, HiSilicon |
| R2-2500970 |
Introduction of Location Coordinate Reference Systems |
Ericsson, AT&T, FirstNet, Deutsche Telekom, MediaTek Inc. |
| R2-2500995 |
CORESET 0 restriction for DL BWP for SDT |
Nokia, InterDigital |
| R2-2501053 |
Discussion on UE aggregation enhancement |
CMCC,ZTE,MediaTek,vivo,Huawei,Meta,CATT |
| R2-2501054 |
Corrections to TS 38.300 on multi-path relay enhancement |
CMCC,ZTE,MediaTek,vivo,Huawei,CATT |
| R2-2501055 |
Corrections to TS 38.321 on multi-path relay enhancement |
CMCC,ZTE,MediaTek,vivo,Huawei,CATT |
| R2-2501056 |
Corrections to TS 38.323 on multi-path relay enhancement |
CMCC,ZTE,MediaTek,vivo,Huawei,CATT |
| R2-2501057 |
Corrections to TS 38.331 on multi-path relay enhancement |
CMCC,ZTE,MediaTek,vivo,Huawei,CATT |
| R2-2501058 |
Corrections to TS 38.306 on multi-path relay enhancement |
CMCC,ZTE,MediaTek,vivo,Huawei,CATT |
| R2-2501078 |
Discussion on packet priority based access control |
SK Telecom, LG Uplus |
| R2-2501113 |
Discussion on the issue of ANR reporting of HSDN cells [ANR_HSDN] |
Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo |
| R2-2501276 |
Re-direction to an NTN frequency |
Samsung |
| R2-2501329 |
Introduction of Location Coordinate Reference Systems |
Ericsson, AT&T, FirstNet, Deutsche Telekom, MediaTek Inc., ESA |
| R2-2501534 |
[DRAFT] LS to RAN1 on BWP restrictions for SDT |
Ericsson |
| 8.19 |
NR Others |
|
| R2-2500034 |
LS on Ku band numerology (R4-2419902; contact: Rumney Telecom) |
RAN4 |
| R2-2500040 |
LS on SSB position restrictions for less-than-5MHz Scells (R4-2420383; contact: Qualcomm) |
RAN4 |
| R2-2500041 |
LS on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx (R4-2420410; contact: CATT) |
RAN4 |
| R2-2500047 |
LS on Location service of UEs served by MWAB (S2-2412625; contact: Huawei) |
SA2 |
| R2-2500087 |
Discussion on RAN4 LS on Ku Band Numerology |
vivo |
| R2-2500113 |
Discussion on n5-n8 simultaneous operation (R4-2420410) |
OPPO |
| R2-2500229 |
Discussion on FDD-FDD inter-band CA simultaneous RxTx (LS R4-2420410) |
CATT, Huawei, HiSilicon, China Telecom, China Unicom |
| R2-2500230 |
DRAFT Reply LS on UE capability for FDD-FDD inter-band CA simultaneous RxTx |
CATT |
| R2-2500694 |
Discussion on Ku band numerology |
Huawei, HiSilicon |
| R2-2500932 |
On UE capability for FDD-FDD inter-band CA simultaneous RxTx |
Ericsson |
| R2-2500937 |
Draft Reply LS on Ku band numerology |
THALES |
| R2-2500950 |
SSB position restrictions for less-than-5MHz SCells |
Qualcomm Incorporated |
| R2-2500979 |
Reply LS on Ku band numerology |
Eutelsat Group |
| R2-2501191 |
Capability signalling for overlapping FDD-FDD inter-band CA |
Nokia |
| R2-2501225 |
Consideration on UE capability for FDD-FDD inter-band CA Simultaneous Rx/Tx |
ZTE Corporation |
| R2-2501387 |
SSB position restrictions for less-than-5MHz SCells |
Qualcomm Incorporated |
| R2-2501389 |
SSB position restrictions for less-than-5MHz SCells |
Qualcomm Incorporated |
| R2-2501445 |
[DRAFT] Reply LS on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx |
CATT |
| R2-2501446 |
Summary of offline-205 for potential UE capability for FDD-FDD inter-band CA (CATT) |
CATT |
| R2-2501530 |
Reply LS on Ku band numerology |
RAN2 |
| R2-2501572 |
Reply LS on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx |
RAN2 |
| 9.1 |
Session on V2X/SL, R19 NES and MOB |
|
| R2-2501331 |
Report from session on V2X/SL, R19 NES and MOB |
Vice Chairman (Samsung) |
| R2-2501392 |
LS to RAN4 on granularity definition of pdcch-RACH-AffectedBandsList-r18 |
RAN2 |
| 9.2 |
Session on R18 MIMOevo, R18 MUSIM, and R19 LP-WUS |
|
| R2-2501332 |
Rel-18 MIMO, Rel-19 MIMO, LPWUS, and SBFD |
Vice Chairman (CATT) |
| 9.3 |
Session on NR NTN and IoT NTN |
|
| R2-2501333 |
Report from session on NR NTN and IoT NTN |
Session chair (ZTE) |
| 9.4 |
Session on positioning and sidelink relay |
|
| R2-2501334 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 9.5 |
Session on R18 MBS, R18 QoE and R19 XR |
|
| R2-2501335 |
Report from session on R18 MBS, R18 QoE and R19 XR |
Session chair (Huawei) |
| 9.6 |
Session on maintenance and SON/MDT |
|
| R2-2501336 |
Report from session on maintenance and SON/MDT |
Session chair (Ericsson) |
| R2-2501438 |
Report from session on maintenance and SON/MDT |
Session chair (Ericsson) |